The Agency

What it is

The Agency is a library of AI agent files from the agency-agents repository. Each agent is one Markdown file that gives your coding tool a role to work in, such as Frontend Developer, Reality Checker, Penetration Tester or Grant Writer. The file holds the agent’s personality, core mission, workflow, deliverables with code examples, and success metrics. An install script copies the files to the place your tool reads, and converts them first where the tool wants another format.

1. You pick a division or a few agents
2. The install script converts the files for your tool
3. It copies them into your tool’s agent folder
4. You name an agent in a session
5. The agent works from its own mission and workflow

Who it suits

People who use an AI tool for more than code and want it to take a defined role. A developer wants a code reviewer, a founder wants a plan for getting users, a security lead wants a threat model. It also suits anyone who reads agent prompts to see how others write them, because every file is plain text you can edit. Skip it if you want one general assistant with no roles.

Where to use it

The installer writes these folders, as its usage text and the README’s per-tool sections give them. It scans your machine and pre-selects the tools it finds.

DeepSeek’s DSH, Hermes, Osaurus and Mistral Vibe have installers too. The maker’s own desktop app installs into several of these tools without a script.

How to set it up

Get it saves a zip of Mindket’s setup notes in your downloads folder, with a page for each tool from the maker’s README and integration pages. The agents install from msitarzewski’s repository, so you need a copy of it first.

1. Get the repository onto your machine and open a terminal in its folder.
2. Run the converter. It writes the files each tool needs.
3. Run the installer. Its wizard has three screens, Tools, Teams and Review: keep your tools ticked, keep or narrow the teams, then press Enter on Install.
4. Start a new session in your tool and name an agent.

./scripts/convert.sh
./scripts/install.sh

Claude Code and GitHub Copilot need no conversion, so one line does it for Claude Code.

./scripts/install.sh --tool claude-code

Cursor, Windsurf, Aider, OpenCode and Qwen Code work from a project, so run the installer from your project’s root by its full path.

cd /your/project
/path/to/agency-agents/scripts/install.sh --tool cursor

To install one division, add --division, and add --dry-run to see the plan without writing anything. Aider and Windsurf get the whole roster in one file whatever you pick, and Hermes ignores --division and --agent, because its router keeps the full roster on disk.

./scripts/install.sh --tool claude-code --division engineering,security
./scripts/install.sh --tool opencode --division engineering --dry-run

The maker’s desktop app, for macOS, Linux and Windows, does the same job with no script. On a Mac the README gives one line to install it.

brew install --cask msitarzewski/agency-agents/agency-agents

How to use it

Name the agent in a session. Claude Code, Copilot and Codex take this plain line from the README. Windsurf and Aider take lines of the same shape.

Use the Frontend Developer agent to review this component.

Other tools have their own way to call an agent. These are lines from the README and the tools’ pages.

Hermes works differently. It gets four routing tools, search, inspect, load and delegate, and you ask it in plain words to use the plugin.

The roster is split into divisions. These are a few agents from the README’s tables.

Example

You build a small web app in Claude Code, and the agents are installed. You type the README’s own line.

Hey Claude, activate Frontend Developer mode and help me build a React component

The README’s claim is that each file gives the agent a defined specialty, voice and process, not a generic prompt. When the component works, you call a second role the same way.

Use the Reality Checker agent to verify this feature is production-ready.

The README’s startup MVP team lists five roles: Frontend Developer, Backend Architect, Growth Hacker, Rapid Prototyper and Reality Checker.

For newcomers and experts

If you are new. An agent here is a text file that tells your AI tool who to be and how to work. It sets a role, rules, steps and what to hand back. In most tools you call the agent by name. In Cursor you call one with @ and its slug, such as @frontend-developer. A rule applies by itself only after you set alwaysApply: true in its frontmatter, as the Cursor page shows. Aider keeps its roster index in context all session. Start with one division and one agent on a real task, then open its file once to see what it asks of the model. Claude Code and Copilot are the easiest first tools, since they need no conversion. Copilot also needs VS Code’s chat.agentFilesLocations setting to include the install folder.

For experts. The agents are one source format, Markdown with YAML frontmatter, and convert.sh builds each tool’s format from it. That is why the same agent is a TOML file for Codex, a SKILL.md for Antigravity and DSH, an .mdc rule for Cursor and a three-file workspace for OpenClaw. The installer also takes --agent and --agents-file for a hand-picked set, and --link to symlink instead of copy. Updates propagate at once for Claude Code and Copilot, which link the agent files themselves. For the other tools they arrive after you rerun convert.sh, because those tools link the converted files in integrations/.

A runbook’s roster can install as a team. The README shows a short Python snippet that reads strategy/runbooks.json and writes the agent ids to a file for --agents-file.

Some limits come from the tools. Aider keeps its conventions file in context all session. It gets a roster index with each agent’s path in place of the agent bodies, and you read one in when you need it. OpenCode registers only part of a large roster, so install a subset with --division. Qwen Code needs 0.25.1 or later, because earlier releases refuse to launch an agent whose code examples contain ${name} placeholders. Hermes gets one router plugin that keeps the roster on disk and loads a specialist only when you ask for one.

Good to know

The agents are text files your tool follows, and the scripts mostly copy and convert them.

• Scope: Claude Code, Copilot, Antigravity, Gemini CLI, Codex, OpenClaw, Kimi Code, Osaurus, Hermes, Mistral Vibe and DSH (by default) install into your home folder. Cursor, Windsurf, Aider, OpenCode and Qwen Code install into the project you run the installer from
• Names: Antigravity, Osaurus and DSH skills carry an agency- prefix, which the Antigravity and DSH pages say keeps them from clashing with skills you already have
• OpenClaw: the installer registers each workspace through your openclaw command when it exists, and you restart the gateway afterwards
• Windows: the scripts are shell scripts, so use Git Bash or WSL
• A moving roster: the README calls it a growing collection, so what you install today is not a fixed set
• Translations: the README links community versions in Simplified Chinese, Portuguese, Russian, Indonesian, Arabic, Korean, Japanese and Vietnamese, each in its own repository and maintained independently of this one. One maintainer, @jnMetaCode, keeps six of them, and Simplified Chinese has two versions
• The app: the desktop app is a separate project, and this listing covers the agents repository only
• License: MIT. The LICENSE file names AgentLand Contributors