# AI use cases for Agency Agents (msitarzewski/agency-agents)

Repo: [msitarzewski/agency-agents](https://github.com/msitarzewski/agency-agents) | Use cases: 3 | Page: https://dedupedai.com/use-cases/msitarzewski-agency-agents/

The Agency is a large collection of specialized AI agent personalities, each with its own expertise, workflow, deliverables and success metrics, organized into divisions such as Engineering, Design, Marketing and Security. An install script and a native desktop app put the agents into Claude Code, Cursor, Codex, Gemini CLI, OpenCode and other tools.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Install a full engineering team of agents into Claude Code: https://dedupedai.com/use-cases/msitarzewski-agency-agents/install-an-engineering-team-into-claude-code/
- Install the exact team a startup MVP runbook calls for: https://dedupedai.com/use-cases/msitarzewski-agency-agents/install-a-startup-mvp-runbook-team/
- Use the same specialist agents in Cursor, Codex or Gemini CLI: https://dedupedai.com/use-cases/msitarzewski-agency-agents/use-agency-agents-in-cursor-or-codex/

## How to install a full engineering team of agents into Claude Code with Agency Agents

Repo: [msitarzewski/agency-agents](https://github.com/msitarzewski/agency-agents) | Difficulty: Beginner | Time: 10 minutes | Basis: From the README

Copy the Engineering and Security divisions into Claude Code and call each specialist by name.

**Who it is for:** A solo developer who wants a frontend developer, backend architect and DevOps automator on call in one terminal.

**The problem:** Generic prompts give generic answers, and writing a good persona for every role takes hours.

**The outcome:** Specialist agents installed in Claude Code that you activate per task, each with its own process and deliverables.

### Steps

1. Clone the repo and run `./scripts/install.sh --list teams` to see every team and agent count
2. Install only what you need with `./scripts/install.sh --tool claude-code --division engineering,security`
3. Or copy one division by hand with `cp engineering/*.md ~/.claude/agents/`
4. In a Claude Code session, ask it to activate Frontend Developer mode for a UI task
5. Switch to Backend Architect or DevOps Automator for API and pipeline work

### Prompt to paste into your agent

```text
Install the msitarzewski/agency-agents Engineering and Security divisions into Claude Code, then use the Backend Architect agent to design the API for <feature> and the Frontend Developer agent to build its UI. Summarize what each agent produced.
```

### Caveat



Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/msitarzewski-agency-agents/install-an-engineering-team-into-claude-code/

## How to install the exact team a startup MVP runbook calls for with Agency Agents

Repo: [msitarzewski/agency-agents](https://github.com/msitarzewski/agency-agents) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Pull a runbook's roster into a team file and install just those agents into your tool.

**Who it is for:** A founder who wants the right mix of agents for an MVP without installing the whole roster.

**The problem:** Installing every agent clutters your tool and, in OpenCode, silently drops agents past its limit.

**The outcome:** Only the agents listed in the startup-mvp runbook, installed in Claude Code and ready to use.

### Steps

1. Clone the repo and open strategy/runbooks.json to see the runbooks and their rosters
2. Run the python one-liner from the README that writes the startup-mvp roster to team.txt
3. Install that roster with `./scripts/install.sh --tool claude-code --agents-file team.txt`
4. Preview any other selection first with `./scripts/install.sh --tool opencode --division engineering --dry-run`
5. Work through your MVP by handing each task to the matching agent

### Prompt to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/msitarzewski-agency-agents/install-a-startup-mvp-runbook-team/

## How to use the same specialist agents in Cursor, Codex or Gemini CLI with Agency Agents

Repo: [msitarzewski/agency-agents](https://github.com/msitarzewski/agency-agents) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Generate integration files for every supported tool and install the agents where you actually work.

**Who it is for:** A developer who switches between Cursor, Codex and Gemini CLI and wants the same specialists in each.

**The problem:** Agent personas written for one tool rarely work in another without manual conversion.

**The outcome:** The same agents converted and installed into each of your tools, picked by name.

### Steps

1. Run `./scripts/convert.sh` to generate integration files for all supported tools
2. Run `./scripts/install.sh` for the interactive wizard that detects what you have installed
3. Or target one tool, for example `./scripts/install.sh --tool cursor --agent frontend-developer,ui-designer`
4. Use `./scripts/install.sh --tool codex` or `./scripts/install.sh --tool gemini-cli` for those agents
5. On a Mac, the desktop app installs and auto-updates the roster with `brew install --cask msitarzewski/agency-agents/agency-agents`

### Prompt to paste into your agent

```text
Convert msitarzewski/agency-agents for Cursor and Codex, install only frontend-developer and ui-designer into Cursor, and confirm both tools list the agents. Then use UI Designer to review <screen>.
```

### Caveat



Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/msitarzewski-agency-agents/use-agency-agents-in-cursor-or-codex/
