Discofork
Repository brief

msitarzewski/agency-agents

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T12:08:02.321Z
3mo ago

msitarzewski/agency-agents

msitarzewski/agency-agents is a large MIT-licensed collection of specialized AI agent prompts/personas, organized as a "complete AI agency" for coding, product, marketing, sales, support, testing, and other workflows. It appears highly active and popular, with 66,173 stars, 9,995 forks, and commits as recent as 2026-03-27. Forks are likely most interesting if you want a broad, opinionated agent library that can be copied into Claude Code or converted for other tools like Cursor, Aider, Windsurf, Gemini CLI, OpenCode, and Kimi Code.

GitHub
Loading tags...
Stars66,173
Forks9,995
Default branchmain
Last pushed2026-03-27T05:36:01Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer upstream unless you specifically want a pinned, unmodified snapshot. This fork adds no visible capabilities and is 94 commits behind, so its value is mostly as a stable starting point rather than a better version of the project.

Choose this fork only if you want a mostly unchanged copy with a tiny README tweak. If you want the freshest agent catalog or active upstream improvements, use upstream instead.

Choose this fork if your main need is a security- and delivery-oriented agent pack. Stay with upstream if you want the newest, broadest, and most actively updated general-purpose agency library.

Prefer upstream unless you specifically want a frozen snapshot. This fork adds nothing new and is already far behind the active upstream, so it is a poor choice for users who want the latest agents, fixes, and workflows.

Prefer this fork only if you want an unchanged snapshot. If you want the newest agents, docs, and community updates, upstream is the better choice.

Choose this fork only if you specifically want an unmodified mirror. If you want the latest agent roster or a fork that adds value for adopters, upstream is the better choice.

Choose this fork only if you specifically want a dormant baseline to extend yourself. If you want the latest agents, workflows, and maintenance from the project, upstream is the better choice.

Prefer upstream unless you specifically want a frozen copy to customize locally; this fork adds no visible capabilities and is behind on active upstream work.

Choose upstream unless you specifically want a lightly maintained snapshot or renamed mirror; this fork does not add functionality and is materially behind.

Prefer upstream unless you specifically want an untouched snapshot to customize yourself. This fork adds nothing yet trails upstream by 45 commits, so it is not the better adoption choice for users who want the latest agents or workflows.