Who it is forA founder who wants the right mix of agents for an MVP without installing the whole roster.
The problemInstalling every agent clutters your tool and, in OpenCode, silently drops agents past its limit.
The outcomeOnly the agents listed in the startup-mvp runbook, installed in Claude Code and ready to use.
What you need first
- A supported tool such as Claude Code, Cursor, Codex, Gemini CLI or OpenCode
- A clone of the repo for the script install, or the Agency Agents desktop app
- OpenCode registers only about 119 agents, so install a subset there
Steps
- Clone the repo and open strategy/runbooks.json to see the runbooks and their rosters
- Run the python one-liner from the README that writes the startup-mvp roster to team.txt
- Install that roster with
./scripts/install.sh --tool claude-code --agents-file team.txt - Preview any other selection first with
./scripts/install.sh --tool opencode --division engineering --dry-run - Work through your MVP by handing each task to the matching agent
Prompt for your agent
Using msitarzewski/agency-agents, extract the startup-mvp runbook roster into team.txt and install it into Claude Code with --agents-file. Then list the installed agents and propose which one should own each part of building <MVP idea>.
Caveat. OpenCode currently registers only about 119 agents and drops the rest; the installer warns you when a selection would exceed that.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for msitarzewski/agency-agents and "Install the exact team a startup MVP runbook calls for"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer