When AI Learns Division of Labor: How a Reddit Post Grew Into a 932-Star AI Agent Company
> Original repository: msitarzewski/agency-agents > Trending data: +932 stars today | Language: Shell | Category: AI agent framework
It Started With a Reddit Post
One day in 2025, someone on Reddit asked a question: what if AI coding assistants like Claude, Cursor, and Codex weren't "general-purpose helpers," but operated like a real agency—with a frontend specialist, a community manager, and a quality gatekeeper?
The post didn't sink. It became a project called The Agency. A few months later, the project hit GitHub Trending, gaining 932 stars in a single day.
Not Prompt Templates—"Persona Profiles"
The market is full of repos like "100 ChatGPT prompts." What makes agency-agents different is that it writes a complete persona profile for each agent.
Every agent file contains four layers of information:
1. Identity and personality traits—who this agent is and how it communicates 2. Core tasks and workflows—what this agent is responsible for and how it works 3. Technical deliverables—what the agent produces, with code examples 4. Success metrics and communication style—how quality is measured and how results are reported
This is not a one-line prompt like "act as a frontend engineer." It's a complete job description: the AI knows who it is, what to do, and what "done well" looks like.
The Org Chart of an "Agent Company"
Agents in the agency-agents repo are organized by function, like a real agency:
- Engineering: frontend developer, backend developer, full-stack engineer
- Community: Reddit community operations, social media strategist
- Creative: Whimsy Injector—a job title that's interesting on its own
- Quality: Reality Checker—whose job is specifically to poke holes
- Claude Code
- Cursor
- GitHub Copilot
- Gemini CLI
- Codex
- Aider
- Windsurf
- OpenClaw
- Kimi Code
- Osaurus
- Hermes
- Mistral Vibe
- Antigravity
The most interesting roles are the "Whimsy Injector" and the "Reality Checker." The former makes the product fun; the latter makes it reliable. Both roles exist in any real creative company, but few AI projects separate them explicitly.
One-Click Installation Into Every Major Tool
agency-agents is not tied to a single tool. It provides a conversion script that transforms agent files into formats for:
What does this mean? Agent personas become portable assets. The "frontend engineer" agent you use in Claude Code can be moved to Cursor unchanged. Persona definitions are decoupled from tool implementations.
Why 932 Stars?
The project's breakout wasn't accidental. It taps into an emerging trend: AI tools evolving from "general assistants" to "expert teams."
The problem with general assistants: they know a little of everything but lack depth. Ask one to write React components and it can; ask it for a Reddit community strategy and it can do that too—but neither output is deeply professional.
agency-agents' solution isn't training more models, but prompt-level specialization and division of labor. Each agent file is the "soul" of a domain expert—containing that domain's workflows, delivery standards, and communication style.
It mirrors how human organizations divide work: you wouldn't ask a full-stack engineer to run community operations, nor a community manager to write frontend code. Specialized work goes to specialists—or specialized agents.
Implications for AI Engineering
agency-agents got one key thing right: separating persona definitions from tool implementations.
Most AI tools treat persona as: system prompt + tool configuration, coupled together—switch tools and you rewrite everything. agency-agents' approach: persona = a single Markdown file. Tools just read that file and adapt to their own format.
This is the same principle as "separation of concerns" in software engineering. Persona definitions are business logic; tool adaptation is infrastructure. Separated, each can evolve independently.
A Question Worth Thinking About
agency-agents ships dozens of predefined agents. But a real agent company wouldn't have only a few dozen roles—it would have hundreds or thousands of specialized positions.
The open question: who defines these agents? Who validates their expertise? Who maintains their quality?
agency-agents offers a starting point. But the endgame of the "AI agent company" concept may be far bigger than a single GitHub repository.
---
*Project: github.com/msitarzewski/agency-agents*