MedevalFyre | Captains Quarters

THIS IS F*CKING INSANE Anthropic turned Agent Skills into an open spec and GitHub filled up with ready-made Claude Code teams for free one of these repos alone ships 135 agents, 35 skills, 42 commands, 176+ plugins and 20 hooks. another hands you 100+ specialized subagents. none of it costs anything 10 GitHub projects you should open first: 01 wshobson/agents → a plugin marketplace that installs the same agents into Claude Code, Codex, Cursor and Copilot, so your setup survives switching tools github.com/wshobson/agents 02 VoltAgent/awesome-claude-code-subagents → 100+ specialized subagents covering most of what a normal engineering week throws at you github.com/VoltAgent/awesome… 03 rohitg00/awesome-claude-code-toolkit → 135 agents, 35 curated skills, 42 commands, 176+ plugins, 20 hooks and 14 MCP configs in one place github.com/rohitg00/awesome-… 04 anthropics/skills → the official Agent Skills repo. start here to see the shape of a working SKILL.md before you copy anyone else's github.com/anthropics/skills 05 netresearch/claude-code-marketplace → curated skills on an open standard, portable across Claude Code, Cursor, Copilot, Codex, Gemini CLI and 30+ other agents github.com/netresearch/claud… 06 disler/claude-code-hooks-mastery → the hooks reference. this is where you learn to make the agent stop on your rules instead of stopping to ask you github.com/disler/claude-cod… 07 karanb192/claude-code-hooks → an installable hooks marketplace split into safety, cost, observability and productivity github.com/karanb192/claude-… 08 affaan-m/claude-swarm → multi-agent orchestration that decomposes the task, coordinates the agents and shows the whole run in a terminal UI github.com/affaan-m/claude-s… 09 am-will/swarms → orchestration shipped as skills, so the coordination loads only when the job actually calls for it github.com/am-will/swarms 10 eugeniughelbur/obsidian-second-brain → persistent memory as plain markdown in an Obsidian vault, shared across Claude Code, Codex and six other agents github.com/eugeniughelbur/ob… give the first team a job with an obvious finish line: one reviewed PR, one researched brief, one failing test turned green then look at how much of that output you actually kept, and what it cost to produce. a bigger roster earns its place when it moves that number the download is free. paying four agents to repeat the same investigation is not save this before you spend another weekend building a config that already exists the article below shows how to keep context small, reuse finished work and contain retries, so more of your budget reaches the finished result ↓