mrkeyoor.com_
Sat 07 Nov 23:40 UTC
LLM Toolsevaluationupdated 14 Oct 2026

agency-agents review

Agency Agents is a collection of editable instructions that give an existing AI assistant a specialist role, such as frontend developer or code reviewer. It supplies role briefs and tool-specific installation scripts so you can stop rewriting the same assignment from scratch.

+1,055stars / 7d
Verdict

Our Agency Agents run installed 35 packages in 6 seconds and built successfully, but tests were skipped because no target existed. Use it as a source of editable specialist briefs inside an assistant you already operate. Choose a workflow framework instead if you need the process itself supplied and enforced.

We ran it

Lab card: what happened when we ran agency-agentsScreenshot of agency-agents (github.com/msitarzewski/agency-agents)
Install✓ · 6s35 packages · 38 MB
Build✓ · 1s
Testsn/ano test script
Known vulns0(pip-audit)
Repo382 files~7,259 lines of source · 4.9 MB · 6 CI workflows

Answers from our run

Does agency-agents build from source?

Dependencies installed in 6 seconds (35 packages), and the build succeeded in 1 seconds. We cloned commit f99f6aa into a clean Debian container with 3 CPUs and no project-specific setup.

Does agency-agents have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does agency-agents have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use agency-agents?

Teams seeking an independent agent service: the README installs instructions into existing host tools, which still supply the model and execution.

What are the alternatives to agency-agents?

Superpowers, BMad Method. Our Agency Agents run installed 35 packages in 6 seconds and built successfully, but tests were skipped because no target existed.

Setup4/56-second lab install; host-tool setup remains separate
Docs4/5Detailed integrations, selectors, and role files need adaptation
Community5/5October 13 push and an active contribution queue
Maturity3/5Usable briefs; skipped tests leave agent behavior unmeasured

Who it’s for

Developers already using Claude Code or another supported coding assistant who want editable specialist briefs.
Teams with an existing review process that can adapt role instructions to their stack.
Users who want to select individual agents or divisions rather than adopt the entire roster.

Who it’s NOT for

Teams seeking an independent agent service: the README installs instructions into existing host tools, which still supply the model and execution.
OpenCode users expecting the entire roster to register: the README warns that the runtime silently drops agents beyond its limit.
Review teams expecting the Reality Checker to match their tooling without edits: its instructions assume specific screenshot scripts and result paths.
Buyers treating a successful build as evidence of agent quality: our lab found no test target and skipped tests.

Setup reality

Our sandbox installed commit f99f6aa in 6 seconds: 35 packages and 38 MB on disk. The build passed in 1 second. Tests were skipped because no script or target existed, and pip-audit reported 0 known vulnerabilities.

Using the role instructions requires an existing supported assistant and its model access or account. Claude Code reads native agent files; several other tools need conversion first. Each task may also need your project tooling, services, and permissions.

The measured Python path is separate from the README's host-tool integrations and desktop app. Installation destinations vary between project and user directories. Select a subset, inspect a dry run, and adapt embedded workflow commands before trusting a role.

The useful part is a brief you can edit

Copy the Frontend Developer instructions into your coding tool and you'll inherit a detailed brief: accessibility requirements, framework choices, code examples, and a review process. Agency Agents collects these briefs across engineering, marketing, design, and other specialties. The appeal is practical. You can read the instructions, remove irrelevant demands, and give an existing assistant a more explicit assignment than a job title alone would provide.

Our checkout contained 382 files and about 7,259 lines of source in 4.9 MB. That makes browsing individual files a reasonable starting point. The library's names and personalities help you find a role, but the useful purchase decision is whether its actual instructions suit your project. The Frontend Developer file, for example, mixes ordinary web work with editor extensions and WebSocket bridges. Read before adopting the whole brief.

What happened when we ran it

Our run installed commit f99f6aa in 6 seconds, adding 35 packages and using 38 MB on disk. The build succeeded in 1 second. We cloned it on October 13, 2026, into an unprivileged Debian container with 3 CPUs, 8 GB of RAM, Python 3.12, and no secrets. Those results show that the Python path selected by our harness completed without an installation or build failure.

The lab found 6 CI workflow files, no Dockerfile, and no tests directory. It skipped tests because there was no test script or target. Pip-audit reported 0 known vulnerabilities. These are checks on the measured environment, not proof that a marketing agent will write accurate copy or that a coding agent will make correct changes. We did not measure agent output quality, token consumption, or the separate desktop application.

Your existing assistant supplies the execution

The README's tool instructions describe native Markdown agents for Claude Code and converted formats for other tools. Cursor receives rule files, while Aider receives a roster index that points to fuller instructions. You still need a working host tool and whatever account or model access it requires. Copying a role file does not supply a model, grant tool access, or connect business systems mentioned in its examples.

The 38 MB we measured therefore shouldn't become a budget for an operating AI team. It describes our installed sandbox environment only. Your coding tool's runtime, model usage, and task-specific services sit outside that figure. A frontend assignment may need your application's dependencies and browser tooling, while a marketing assignment needs source material and publishing permissions. Decide what the assistant may do before letting a role's workflow direct its actions.

Install selected roles before adopting a whole roster

The README provides division and individual-agent selectors, plus a dry-run option. Those controls matter because tool integrations behave differently. Aider's conventions file indexes roles instead of loading every full prompt into the session. Windsurf combines the agents into a rules file. Project-scoped destinations also differ from global ones, so a library copied for one repository can have a different reach from agents installed under your home directory.

The 382-file checkout gives you plenty to filter without treating every file as useful context. I'd start with a role whose output you already know how to judge, then remove requirements that belong to another stack. The README also warns that OpenCode can silently omit agents beyond its registration limit and recommends installing a subset. That warning is a concrete reason to avoid a whole-roster deployment, even when the conversion scripts complete.

The Reality Checker assumes its own evidence files

The Reality Checker instructions ask for screenshots and refer to a particular capture script, output directory, and result file. Requiring evidence is useful. Expecting those exact artifacts in an unrelated application is less useful unless you adapt the instructions. A team with an established browser suite should replace the assumed commands and paths with its own before relying on the resulting assessment.

Our 1-second build cannot validate those embedded workflows, and the skipped test step leaves their behavior unmeasured. The same caution applies to instructions that tell a model to remember past patterns: wording about memory doesn't establish durable storage in your chosen host. This library is easiest to recommend to someone who will edit the briefs. It is harder to recommend as a ready-made process for unattended approvals across unfamiliar projects.

October activity supports use, without proving outcomes

GitHub listed 159,932 stars and 207 open issues and PRs on October 14, 2026. The last push was October 13, and recent pull requests addressed concrete content problems, including analytics calculations and source provenance. The latest-release endpoint returned no release for this repository. Together, the push date and current contribution queue show ongoing work, while the absence of a release tag gives you less help choosing a fixed packaged edition.

Our 6-second install makes a local trial inexpensive. Pin the instructions you evaluate rather than letting a successful experiment silently inherit later edits. MIT licensing permits adaptation, but neither the license nor the contribution volume certifies the output. Keep the host model and project context fixed when comparing an edited role against your existing instructions, and judge the result by the work you actually needed done.

Choose a workflow framework if role briefs aren't enough

Superpowers centers its documentation on design, implementation plans, and reviewed development tasks. BMad Method carries briefs and architecture through a delivery process. Choose one of those when the missing piece is an ordered engineering method. Agency Agents fits better when you already have a method and want readable specialist instructions to adapt within it. Keep the Frontend Developer's requirements that match your application, and delete the editor-bridge assignment if you aren't building an editor bridge.

Alternatives

ProjectWhat it isPick it when
Superpowers gh↗A coding-agent skill framework organized around design, planning, and reviewed implementation.pick this instead when you need an ordered development method more than a broad role library.
BMad Method gh↗An AI-assisted delivery method that carries briefs and architecture into implementation.pick this instead when product definition and project-wide delivery decisions need a shared workflow.

What people are saying

  1. [github-trending] msitarzewski/agency-agents-app
  2. [github-trending] msitarzewski/agency-agents

Sources

  1. Agency Agents README and integration instructions
  2. Frontend Developer role file
  3. Reality Checker role file
  4. Agency Agents recent issues and pull requests
  5. Superpowers README
  6. BMad Method README

More llm tools reviews

MCPJungle · octomind · kimi-k3-in-c · nanochat · FreeToken · ironclaw · the whole board →