Intake notes: listed with facts from the source repo; not yet vetted. A verdict waits on a real hands-on audit (install, run, audit what it injects). Health is checked automatically; the summary is the author’s own description.
awesome-claude-code
• Not yet vettedA hand-picked collection of the finest of resources for the most awesome of agents, Claude Code, the undisputed champion of coding companions, from the unstoppable team at…
In the intake queue. Listed with facts only; no verdict until a human runs it.
by hesreallyhim plugin Workflows
Shipped today passing liveness · checked Jul 28, 2026
Commit activity · last 52 weeks
Stars51k
LanguagePython
Open issues721
Pricingfree
ListedJul 12, 2026
Facts pulled from the source repo and refreshed nightly. Stars are a data point, not our ranking. We don't order by popularity.
Runs in
| Harness | Support | Notes |
|---|---|---|
| Claude Code | untested | — |
Support levels reflect what we actually ran, not what the README claims. untested means exactly that.
What a vet will check
- The always-on context cost across everything the plugin bundles
- Whether triggers are scoped or fire too eagerly
- What each bundled skill or command injects
No verdict is published until a human installs it, runs it, and audits what it injects. How vetting works →
More in Workflows
cc-skills skill “Twenty skills, about 4,000 always-on tokens measured with tiktoken (~200 each), because until a skill fires only its one-line description is loaded. The scoping is better than most: descriptions say "use when X" and "do not use for Y," and cross-reference their siblings. The catch is the default install. Both the marketplace path and the CLI's --all load all 20, and a few triggers are deliberately greedy (frontend-design-deslop fires on "build a UI for X," deep-research on "look into X," copywriting-hooks on the word "hook"), so they fire on generic requests. Install the ones you want by name with --skill instead of taking the whole set. No scripts, no network calls of its own, no telemetry, MIT. Clean, with a cost you should choose on purpose.”
superpowers plugin “The discipline pack, and it's honest about its cost. Fourteen skills (brainstorming, test-driven development, systematic debugging, plan writing, git worktrees), and the whole set adds only about 577 tokens of always-on context, measured with tiktoken, because until a skill fires, its one-line description is all that's loaded. The scoping is tight. Most descriptions are "use when…" triggers, so they stay quiet until they're relevant. One stylistic heads-up rather than a fault: a few are written as hard commands ("You MUST use this before any creative work"), which will nudge the model firmly. That's the point if you want the guardrails, worth knowing if you don't. Progressive disclosure done the way the mechanism intends.”
claude-code-subagents subagent “Seven subagents (code refactorer, frontend designer, PRD writer, security auditor, and more) with genuinely useful system prompts, held back by stale packaging. One commit, dated 2025-07-25, and it shows. The tool grants are the problem. Three agents (content-writer, frontend-designer, vibe-coding-coach) declare no tools: line, so they inherit every tool including Bash and web access. The security-auditor is granted Write and Edit but no Read, an auditor that can rewrite your files while shelling out to read them. The project-task-planner is told in its own prompt it is "not allowed to action any tasks," then handed Bash, Write, and Edit anyway. Add deprecated tool names (MultiEdit, LS) and two agents whose examples call themselves by names that no longer match. The prompts are worth reading. Copy the one or two you have reviewed into .claude/agents/, set each agent's tools: to the minimum it needs, and do not bulk-install the folder.”
wshobson/agents subagent A large catalog of production-focused Claude Code subagents: reviewers, architects, and language specialists, installed per project or globally.