Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/mblua/agentscommander/agency-agents-rolesnpx skills add mblua/AgentsCommander --skill agency-agents-rolesgit clone --depth 1 https://github.com/mblua/AgentsCommanderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mblua/agentscommander/agency-agents-roles)<a href="https://agentmods.dev/skills/mblua/agentscommander/agency-agents-roles"><img src="https://agentmods.dev/badge/skills/mblua/agentscommander/agency-agents-roles.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00056 | $0.00526 |
| Opus 5 | $0.00028 | $0.00263 |
| Sonnet 5 | $0.00011 | $0.00105 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
agency-agents-roles scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
agency-agents-roles
Mandatory offer before creating a specialist agent
Before you create any new specialist agent (any role-defined create-agent-matrix), you MUST first offer Agency Agents role templates.
Skip the offer ONLY if, in this session, the user already declined Agency templates or explicitly asked for a custom or from-scratch role.
Say what Agency Agents is, from real data only
When you offer, briefly say what Agency Agents is, but state ONLY what real local data supports. Never invent a description or recall one from memory.
- Agency Agents is a collection of tested, shareable role templates published in a source repository. The real source is the
repovalue reported byagency-templates status(and stored in the cache manifest), not a URL you guess. - Describe Agency Agents concretely by its source repo plus the actual templates available (their real names and 1-line descriptions from
agency-templates list); there is no local one-line project description to quote. - If the template cache is absent (status reports it unavailable), say so and offer to fetch it. Ask before downloading or updating, because it writes to the local template cache.
On acceptance, use the CLI
Use the AgentsCommander CLI from AGENTSCOMMANDER_BINARY_PATH:
"<AGENTSCOMMANDER_BINARY_PATH>" agency-templates update --ref main
"<AGENTSCOMMANDER_BINARY_PATH>" agency-templates status --pretty
"<AGENTSCOMMANDER_BINARY_PATH>" agency-templates list --pretty
update refreshes the local cache from the source repo (--ref selects the git ref, default main). status reports whether a cache is present and its repo, ref, and commit. list prints each cached template's real id and 1-line description.
Then present the candidate template(s) and create with create-agent-matrix --role-template <id>. Use only the IDs and descriptions that command returns; never invent template IDs or descriptions.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 34 lines · 56 tokens per session scan A 30431b8b39ba
agency-agents-roles is a skill published in the GitHub repository mblua/AgentsCommander (10 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 526 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
qa-cli-mcp-api
Select and run explicitly requested, risk-based QA for Anarlog's CLI, webhooks, stdio MCP, hosted Cloud API, and remote MCP. Test only affected lanes unless comprehensive coverage is requested.
sqlite-schema-design
Design or review schemas for crates/cloudsync using SQLite Sync constraints, not generic SQLite advice. Use when adding synced tables, changing synced columns, or planning CloudSync-safe migrations.
add-plugin
Scaffold a new Tauri plugin in this repository when asked to add or create a plugin under plugins/. Use this for plugin generation and repository integration work, not for editing an existing plugin unless the request is specifically about bringing a freshly generated plugin in line with project conventions.
axum-test-transport
Choose between in-process tower::ServiceExt::oneshot tests and real tokio::net::TcpListener server tests for Axum services in this repository.
new-changelog
Create the next desktop changelog entry when asked to add a changelog file or prepare the next release note under packages/changelog/content. Use this when the task is specifically about determining the next version and creating the markdown entry.
migrate-to-sqlite
Migrate a TinyBase table to SQLite. Use when asked to move a data domain (e.g. templates, vocabs) from the TinyBase store to the app SQLite database.