๐Ÿ‡ฐ๐Ÿ‡ท ํ•œ๊ตญ์–ด ์ž๋งค ํŽ˜์ด์ง€๋Š” ๋ฐœํ–‰ ํ›„ ๋ณ„๋„ ๋งํฌ โ€” Korean sister page added after publish.

<aside> ๐ŸŽฏ

TL;DR โ€” In a single week of May 2026 GitHub accumulated ~290k stars and gained ~73k new ones, and not one of the trending Top 10 was a "bigger model." Every slot went to perimeter components for AI agents (memory, code index, on-device TTS, stealth browser, twelve-factor manifesto) and local-first infrastructure. The "ask one model, get one answer" era is quietly giving way to "a team of specialist agents collaborating on the work."

</aside>

<aside> ๐Ÿ“Š

[Image #1 โ€” Hero] GitHub Trending Top 10 of May 2026 โ€” a map of the agent-era perimeter</strong>

file: 2026-05-31-gh10-hero.png

</aside>


๐Ÿ“Œ Intro โ€” why "Top 10" is interesting

Who this is for โ€” Indie developers picking new tools for side projects, decision-makers planning internal agent infrastructure, and anyone who wants a single-paragraph summary of "what to look at this month."

GitHub Trending refreshes weekly, but aggregating a month reveals the developer community's priorities at that moment. The signal from May 2026 is unambiguous โ€” none of the Top 10 was a large model itself. All ten are around the model: components, infrastructure, tooling.

The Top 10 cluster into four meta-trends.

Meta-trend Member repos Core message
1. Agent infrastructure codegraph ยท agentmemory ยท 12-factor-agents Agent context, memory, and architecture principles outweigh the model itself
2. Vertical specialist Skills academic-research-skills ยท ViMax ยท obra/superpowers Bundled domain-specific Skills beat a generalist model
3. On-device / local-first openhuman ยท supertonic ยท RuView Reclaim data and compute from the cloud back to the device
4. Automation infrastructure bun The foundation that high-throughput agent servers stand on

Quick glossary:


๐Ÿฅ‡ Tier 1 โ€” Agent infrastructure (Memory ยท Index ยท Architecture)

1. codegraph โ€” semantic index for your codebase

colbymchenry/codegraph ยท TypeScript ยท 21,035โ˜… (+14,100/week)

Instead of having a coding agent open files one-by-one to build context for every request, it queries a pre-indexed semantic graph. The pitch: cut token consumption at enterprise scale by an order of magnitude.

When to use: large monorepos where Claude Code / Cursor token costs are biting, or PR review bots whose average response time has crept up.