Coding Agents Get Their Own Infrastructure: 8 Trending Projects, 1.35M Stars, 14 Months
Choosing agent infrastructure now demands a new checklist: evaluate issues, release cadence, and permissions, not star counts. The ceiling on AI coding quality depends on how teams structure context and process, making skill packs the new risk surface and the new competitive layer.
GitHub Trending's top 20 on Nov 19, 2026, was dominated by 8 projects building infrastructure for coding agents. Combined they hold about 1.35 million stars, and all were created within the last 14 months. Star counts were pulled directly from the GitHub API; the projects were filtered out if they produced business value themselves. The rest split into three abstraction layers: L1 skills and methodology (superpowers, ECC, Claude-BugHunter, modern-web-guidance), L2 orchestration (orca, t3code), and L3 harness and runtime (dsh-Go, rea). All sit on top of the same base: Claude Code, Codex CLI, and Cursor CLI.
Three preconditions made this boom possible: CLI agent interfaces converged on the same primitives, MCP unified tool protocols, and the bottleneck shifted from model intelligence to context quality. The article includes a concrete skill-pack structure and warns that stars don't equal usage, that skill packs are a supply chain attack surface, and that context bloat from too many skills kills agents. It proposes a three-step adoption plan: copy the directory structure, verify permissions, and run a controlled experiment with and without skills.
The judgment is that competition is not at the model layer but at standardizing context and process. That depends on three preconditions: top-model gaps continue shrinking, CLI interfaces stay compatible, and MCP avoids fragmentation. If any breaks, half of these projects lose their reason to exist. The previous AI wave sold shovels (compute and models); this one sells instruction manuals for shovels.
The 468K stars on rea, a repo created in April 2026, outpace most established frameworks; at this stage stars measure hype, not maturity.
Skill packs are a new supply chain vector because their instructions are executed by agents with the user's permissions; reviewing them must be as strict as reviewing a shell script.
The article's three preconditions are a falsifiable test: if top-model capability gaps widen, CLI interfaces fragment, or MCP splits into incompatible protocols, half of these projects become obsolete.
Most of the 8 projects are single-person maintenance and under a year old; teams betting on them should check for CI, issue templates, and recent merged PRs.