๐ญ The Agency: AI Specialists Ready to Transform Your Workflow
A complete AI agency at your fingertips - From frontend wizards to Reddit community ninjas, from whimsy injectors to reality checkers. Each agent is a specialized expert with personality, processes, and proven deliverables.
๐ There's an app now
Agency Agents is a native app for macOS, Linux & Windows that browses the entire roster and installs it into Claude Code, Cursor, Codex, Gemini, Osaurus, and more โ with a click. No clone, no scripts, and it auto-updates.
๐ What Is This?
Born from a Reddit thread and months of iteration, The Agency is a growing collection of meticulously crafted AI agent personalities. Each agent is:
- ๐ฏ Specialized: Deep expertise in their domain (not generic prompt templates)
- ๐ง Personality-Driven: Unique voice, communication style, and approach
- ๐ Deliverable-Focused: Real code, processes, and measurable outcomes
- โ Production-Ready: Battle-tested workflows and success metrics
Think of it as: Assembling your dream team, except they're AI specialists who never sleep, never complain, and always deliver.
โก Quick Start
Option 1: Install the app (Recommended)
The fastest way in โ no clone, no terminal. Agency Agents is a native desktop app (macOS ยท Linux ยท Windows) that browses the whole roster and installs agents into Claude Code, Cursor, Codex, Gemini CLI, OpenCode, Qwen, and Osaurus for you, then keeps them up to date.
โฌ Download the latest release โ or on a Mac:
brew install --cask msitarzewski/agency-agents/agency-agents
Prefer the command line? The script-based options below install the same agents.
Option 2: Use with Claude Code
# Install all agents to your Claude Code directory
./scripts/install.sh --tool claude-code
# Or manually copy a category if you only want one division
cp engineering/*.md ~/.claude/agents/
# Then activate any agent in your Claude Code sessions:
# "Hey Claude, activate Frontend Developer mode and help me build a React component"
Option 3: Use as Reference
Each agent file contains:
- Identity & personality traits
- Core mission & workflows
- Technical deliverables with code examples
- Success metrics & communication style
Browse the agents below and copy/adapt the ones you need!
Option 4: Use with Other Tools (GitHub Copilot, Antigravity, Gemini CLI, OpenCode, OpenClaw, Cursor, Aider, Windsurf, Kimi Code, Codex, Osaurus, Hermes, Mistral Vibe, DeepSeek Harness)
# Step 1 -- generate integration files for all supported tools
./scripts/convert.sh
# Step 2 -- install interactively (auto-detects what you have installed)
./scripts/install.sh
# Or target a specific tool directly
./scripts/install.sh --tool antigravity
./scripts/install.sh --tool gemini-cli
./scripts/install.sh --tool opencode
./scripts/install.sh --tool copilot
./scripts/install.sh --tool openclaw
./scripts/install.sh --tool cursor
./scripts/install.sh --tool aider
./scripts/install.sh --tool windsurf
./scripts/install.sh --tool kimi
./scripts/install.sh --tool codex
./scripts/install.sh --tool osaurus
./scripts/install.sh --tool hermes
./scripts/install.sh --tool vibe
./scripts/install.sh --tool dsh
Install only the teams you need (not everyone wants every division):
./scripts/install.sh # interactive wizard: pick tools + teams
./scripts/install.sh --tool claude-code --division engineering,security
./scripts/install.sh --tool cursor --agent frontend-developer,ui-designer
./scripts/install.sh --list teams # see every team + agent count
./scripts/install.sh --tool opencode --division engineering --dry-run
--agent and --agents-file take an agent's slug (as --list agents prints it), its display name, or its file name without .md โ the id the runbook rosters use โ so a runbook's team installs as listed:
python3 -c 'import json, sys
for r in json.load(open("strategy/runbooks.json"))["runbooks"]:
if r["slug"] == sys.argv[1]: [print(a) for g in r["roster"] for a in g["agents"]]' startup-mvp > team.txt
./scripts/install.sh --tool claude-code --agents-file team.txt
OpenCode note: OpenCode's runtime currently registers only ~119 agents and silently drops the rest (upstream bug). Installing a subset with
--divisionkeeps you under that limit. The installer warns you when a selection would exceed it.
See the Multi-Tool Integrations section below for full details.
๐จ The Agency Roster
๐ป Engineering Division
Building the future, one commit at a time.
๐จ Design Division
Making it beautiful, usable, and delightful.
๐ฐ Paid Media Division
Turning ad spend into measurable business outcomes.
๐ผ Sales Division
Turning pipeline into revenue through craft, not CRM busywork.
๐ข Marketing Division
Growing your audience, one authentic interaction at a time.
๐ Product Division
Building the right thing at the right time.
๐ฌ Project Management Division
Keeping the trains running on time (and under budget).
๐งช Testing Division
Breaking things so users don't have to.
๐ Security Division
Defending the stack โ from secure-by-design architecture to breach response.
๐ Support Division
The backbone of the operation.
๐ฅฝ Spatial Computing Division
Building the immersive future.
๐ฏ Specialized Division
The unique specialists who don't fit in a box.
๐ต Finance Division
Accounting, financial analysis, tax strategy, and investment research specialists.
๐ฎ Game Development Division
Building worlds, systems, and experiences across every major engine.
Cross-Engine Agents (Engine-Agnostic)
Unity
Unreal Engine
Godot
Blender
Roblox Studio
๐ Academic Division
Scholarly rigor for world-building, storytelling, and narrative design.
๐ GIS Division
Mapping the Earth, analyzing the built world, and extracting intelligence from geospatial data.
๐ฅ Healthcare Division
Building AI agents for regulated clinical and sovereign health contexts.
๐ Research Division
Finding, evaluating, and synthesizing existing evidence rather than generating new primary data.
๐ฏ Real-World Use Cases
Scenario 1: Building a Startup MVP
Your Team:
- ๐จ Frontend Developer - Build the React app
- ๐๏ธ Backend Architect - Design the API and database
- ๐ Growth Hacker - Plan user acquisition
- โก Rapid Prototyper - Fast iteration cycles
- ๐ Reality Checker - Ensure quality before launch
Result: Ship faster with specialized expertise at every stage.
Scenario 2: Marketing Campaign Launch
Your Team:
- ๐ Content Creator - Develop campaign content
- ๐ฆ Twitter Engager - Twitter strategy and execution
- ๐ธ Instagram Curator - Visual content and stories
- ๐ค Reddit Community Builder - Authentic community engagement
- ๐ Analytics Reporter - Track and optimize performance
Result: Multi-channel coordinated campaign with platform-specific expertise.
Scenario 3: Enterprise Feature Development
Your Team:
- ๐ Senior Project Manager - Scope and task planning
- ๐ Senior Developer - Complex implementation
- ๐จ UI Designer - Design system and components
- ๐งช Experiment Tracker - A/B test planning
- ๐ธ Evidence Collector - Quality verification
- ๐ Reality Checker - Production readiness
Result: Enterprise-grade delivery with quality gates and documentation.
Scenario 4: Paid Media Account Takeover
Your Team:
- ๐ Paid Media Auditor - Comprehensive account assessment
- ๐ก Tracking & Measurement Specialist - Verify conversion tracking accuracy
- ๐ฐ PPC Campaign Strategist - Redesign account architecture
- ๐ Search Query Analyst - Clean up wasted spend from search terms
- โ๏ธ Ad Creative Strategist - Refresh all ad copy and extensions
- ๐ Analytics Reporter (Support Division) - Build reporting dashboards
Result: Systematic account takeover with tracking verified, waste eliminated, structure optimized, and creative refreshed โ all within the first 30 days.
Scenario 5: Full Agency Product Discovery
Your Team: All 8 divisions working in parallel on a single mission.
See the Nexus Spatial Discovery Exercise -- a complete example where 8 agents (Product Trend Researcher, Backend Architect, Brand Guardian, Growth Hacker, Support Responder, UX Researcher, Project Shepherd, and XR Interface Architect) were deployed simultaneously to evaluate a software opportunity and produce a unified product plan covering market validation, technical architecture, brand strategy, go-to-market, support systems, UX research, project execution, and spatial UI design.
Result: Comprehensive, cross-functional product blueprint produced in a single session. More examples.
Scenario 6: Smart Campus Digital Twin
Your Team:
- ๐ง Technical Consultant - Define the digital twin strategy: BIM for buildings, GIS for campus, IoT for real-time
- ๐๏ธ BIM/GIS Specialist - Convert Revit building models to GIS scene layers, design indoor floor plans
- ๐ธ Drone/Reality Mapping - Fly the campus, generate orthomosaic and 3D mesh for context
- ๐ Web GIS Developer - Build the campus dashboard with MapLibre, building layer, and room finder
- ๐๏ธ 3D & Scene Developer - Create immersive 3D scene with terrain, buildings, and flyover tour
- ๐ค GeoAI/ML Engineer - Extract building footprints and tree canopy from drone imagery
- โ GIS QA Engineer - Validate data accuracy, check topology, verify CRS consistency
Result: A campus digital twin that combines BIM detail, drone reality capture, 3D visualization, and web accessibility โ delivered by coordinated specialists in a single pipeline.
๐ค Contributing
We welcome contributions! Here's how you can help:
Add a New Agent
- Fork the repository
- Create a new agent file in the appropriate category
- Follow the agent template structure:
- Frontmatter with name, description, color
- Identity & Memory section
- Core Mission
- Critical Rules (domain-specific)
- Technical Deliverables with examples
- Workflow Process
- Success Metrics
- Submit a PR with your agent
Improve Existing Agents
- Add real-world examples
- Enhance code samples
- Update success metrics
- Improve workflows
Share Your Success Stories
Have you used these agents successfully? Share your story in the Discussions!
๐ Agent Design Philosophy
Each agent is designed with:
- ๐ญ Strong Personality: Not generic templates - real character and voice
- ๐ Clear Deliverables: Concrete outputs, not vague guidance
- โ Success Metrics: Measurable outcomes and quality standards
- ๐ Proven Workflows: Step-by-step processes that work
- ๐ก Learning Memory: Pattern recognition and continuous improvement
๐ What Makes This Special?
Unlike Generic AI Prompts:
- โ Generic "Act as a developer" prompts
- โ Deep specialization with personality and process
Unlike Prompt Libraries:
- โ One-off prompt collections
- โ Comprehensive agent systems with workflows and deliverables
Unlike AI Tools:
- โ Black box tools you can't customize
- โ Transparent, forkable, adaptable agent personalities
๐จ Agent Personality Highlights
"I don't just test your code - I default to finding 3-5 issues and require visual proof for everything."
-- Evidence Collector (Testing Division)
"You're not marketing on Reddit - you're becoming a valued community member who happens to represent a brand."
-- Reddit Community Builder (Marketing Division)
"Every playful element must serve a functional or emotional purpose. Design delight that enhances rather than distracts."
-- Whimsy Injector (Design Division)
"Let me add a celebration animation that reduces task completion anxiety by 40%"
-- Whimsy Injector (during a UX review)
๐ Stats
- ๐ญ 230+ Specialized Agents across every division
- ๐ 10,000+ lines of personality, process, and code examples
- โฑ๏ธ Months of iteration from real-world usage
- ๐ Battle-tested in production environments
- ๐ฌ 50+ requests in first 12 hours on Reddit
๐ Multi-Tool Integrations
The Agency works natively with Claude Code, and ships conversion + install scripts so you can use the same agents across every major agentic coding tool.
Supported Tools
- Claude Code โ native
.mdagents, no conversion needed โ~/.claude/agents/ - GitHub Copilot โ native
.mdagents, no conversion needed โ~/.github/agents/+~/.copilot/agents/ - Antigravity โ
SKILL.mdper agent โ~/.gemini/config/skills/ - Gemini CLI --
.mdagent files ->~/.gemini/agents/ - OpenCode โ
.mdagent files โ.opencode/agents/ - Cursor โ
.mdcrule files โ.cursor/rules/ - Aider โ
CONVENTIONS.mdroster index โ./CONVENTIONS.md - Windsurf โ single
.windsurfrulesโ./.windsurfrules - OpenClaw โ
SOUL.md+AGENTS.md+IDENTITY.mdper agent - Qwen Code โ
.mdSubAgent files โ~/.qwen/agents/ - Kimi Code โ YAML agent specs โ
~/.config/kimi/agents/ - Codex โ TOML custom agents โ
~/.codex/agents/ - Osaurus --
SKILL.mdskills ->~/.osaurus/skills/ - Hermes -- lazy-router plugin ->
~/.hermes/plugins/ - DeepSeek Harness โ
SKILL.mdskills โ~/.dsh/skills/(user) or.dsh/skills/(project)
โก Quick Install
Step 1 -- Generate integration files:
./scripts/convert.sh
# Faster (parallel, output order may vary): ./scripts/convert.sh --parallel
Step 2 -- Install (interactive, auto-detects your tools):
./scripts/install.sh
# Faster (parallel, output order may vary): ./scripts/install.sh --no-interactive --parallel
The installer scans your system for installed tools, shows a checkbox UI, and lets you pick exactly what to install:
+------------------------------------------------+
| The Agency -- Tool Installer |
+------------------------------------------------+
System scan: [*] = detected on this machine
[x] 1) [*] Claude Code (claude.ai/code)
[x] 2) [*] Copilot (~/.github + ~/.copilot)
[x] 3) [*] Antigravity (~/.gemini/antigravity)
[ ] 4) [ ] Gemini CLI (~/.gemini/agents)
[ ] 5) [ ] OpenCode (opencode.ai)
[ ] 6) [ ] OpenClaw (~/.openclaw/agency-agents)
[x] 7) [*] Cursor (.cursor/rules)
[ ] 8) [ ] Aider (CONVENTIONS.md)
[ ] 9) [ ] Windsurf (.windsurfrules)
[ ] 10) [ ] Qwen Code (~/.qwen/agents)
[ ] 11) [ ] Kimi Code (~/.config/kimi/agents)
[ ] 12) [ ] Codex (~/.codex/agents)
[ ] 13) [ ] Osaurus (~/.osaurus/skills)
[ ] 14) [ ] Hermes (~/.hermes/plugins)
[1-14] toggle [a] all [n] none [d] detected
[Enter] install [q] quit
Or install a specific tool directly:
./scripts/install.sh --tool cursor
./scripts/install.sh --tool opencode
./scripts/install.sh --tool openclaw
./scripts/install.sh --tool antigravity
./scripts/install.sh --tool codex
./scripts/install.sh --tool osaurus
./scripts/install.sh --tool hermes
Non-interactive (CI/scripts):
./scripts/install.sh --no-interactive --tool all
Faster runs (parallel) โ On multi-core machines, use --parallel so each tool is processed in parallel. Output order across tools is non-deterministic. Works with both interactive and non-interactive install: e.g. ./scripts/install.sh --interactive --parallel (pick tools, then install in parallel) or ./scripts/install.sh --no-interactive --parallel. Job count defaults to nproc (Linux), sysctl -n hw.ncpu (macOS), or 4; override with --jobs N.
./scripts/convert.sh --parallel # convert all tools in parallel
./scripts/convert.sh --parallel --jobs 8 # cap parallel jobs
./scripts/install.sh --no-interactive --parallel # install all detected tools in parallel
./scripts/install.sh --interactive --parallel # pick tools, then install in parallel
./scripts/install.sh --no-interactive --parallel --jobs 4
Tool-Specific Instructions
Agents are copied directly from the repo into ~/.claude/agents/ -- no conversion needed.
./scripts/install.sh --tool claude-code
Then activate in Claude Code:
Use the Frontend Developer agent to review this component.
See integrations/claude-code/README.md for details.
Agents are copied directly from the repo into ~/.github/agents/ and ~/.copilot/agents/ -- no conversion needed.
./scripts/install.sh --tool copilot
Then activate in GitHub Copilot:
Use the Frontend Developer agent to review this component.
See integrations/github-copilot/README.md for details.
Each agent becomes a skill in ~/.gemini/config/skills/agency-<slug>/.
./scripts/install.sh --tool antigravity
Activate in Gemini with Antigravity:
@agency-frontend-developer review this React component
See integrations/antigravity/README.md for details.
Installs as Gemini CLI subagents. On a fresh clone, generate the Gemini agent files before running the installer.
./scripts/convert.sh --tool gemini-cli
./scripts/install.sh --tool gemini-cli
See integrations/gemini-cli/README.md for details.
Agents are placed in .opencode/agents/ in your project root (project-scoped).
cd /your/project
/path/to/agency-agents/scripts/install.sh --tool opencode
Or install globally:
mkdir -p ~/.config/opencode/agents
cp integrations/opencode/agents/*.md ~/.config/opencode/agents/
Activate in OpenCode:
@backend-architect design this API.
See integrations/opencode/README.md for details.
Each agent becomes a .mdc rule file in .cursor/rules/ of your project.
cd /your/project
/path/to/agency-agents/scripts/install.sh --tool cursor
Rules are auto-applied when Cursor detects them in the project. Reference them explicitly:
Use the @security-engineer rules to review this code.
See integrations/cursor/README.md for details.
CONVENTIONS.md is the roster index โ every agent's name, description, and the
path to its full instructions. Aider keeps a conventions file in context for the
whole session, and the full agent bodies together are about a million tokens, so the
file lists the agents rather than inlining them.
cd /your/project
/path/to/agency-agents/scripts/install.sh --tool aider
Then reference agents in your Aider session:
Use the Frontend Developer agent to refactor this component.
When you want an agent's full instructions, read its file in:
/read-only /path/to/agency-agents/engineering/engineering-frontend-developer.md
See integrations/aider/README.md for details.
All agents are compiled into .windsurfrules in your project root.
cd /your/project
/path/to/agency-agents/scripts/install.sh --tool windsurf
Reference agents in Windsurf's Cascade:
Use the Reality Checker agent to verify this is production ready.
See integrations/windsurf/README.md for details.
Each agent becomes a workspace with SOUL.md, AGENTS.md, and IDENTITY.md in ~/.openclaw/agency-agents/.
./scripts/convert.sh --tool openclaw
./scripts/install.sh --tool openclaw
If the openclaw CLI is available, the installer registers each workspace automatically.
Run openclaw gateway restart after installation so the new agents are activated.
See integrations/openclaw/README.md for details.
SubAgents are installed to .qwen/agents/ in your project root (project-scoped).
Requires Qwen Code 0.25.1 or later. Earlier releases can't launch agents whose code examples contain
${โฆ}placeholders (#1081).
# Convert and install (run from your project root)
cd /your/project
./scripts/convert.sh --tool qwen
./scripts/install.sh --tool qwen
Usage in Qwen Code:
- Reference by name:
Use the frontend-developer agent to review this component - Or let Qwen auto-delegate based on task context
- Manage via
/agentscommand in interactive mode
๐ Qwen SubAgents Docs
Agents are converted to Kimi Code CLI format (YAML + system prompt) and installed to ~/.config/kimi/agents/.
# Convert and install
./scripts/convert.sh --tool kimi
./scripts/install.sh --tool kimi
Usage with Kimi Code:
# Use an agent
kimi --agent-file ~/.config/kimi/agents/frontend-developer/agent.yaml
# In a project
kimi --agent-file ~/.config/kimi/agents/frontend-developer/agent.yaml \
--work-dir /your/project \
"Review this React component"
See integrations/kimi/README.md for details.
Each agent is converted into a Codex custom agent TOML file and installed to ~/.codex/agents/.
./scripts/convert.sh --tool codex
./scripts/install.sh --tool codex
Then reference the custom agent by name in Codex:
Use the Frontend Developer agent to review this component.