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 agents/bobmatnyc/claude-mpm/security_auditorgit clone --depth 1 https://github.com/bobmatnyc/claude-mpmWrote 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/agents/bobmatnyc/claude-mpm/security_auditor)<a href="https://agentmods.dev/agents/bobmatnyc/claude-mpm/security_auditor"><img src="https://agentmods.dev/badge/agents/bobmatnyc/claude-mpm/security_auditor.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.00015 | $0.01124 |
| Opus 5 | $0.00008 | $0.00562 |
| Sonnet 5 | $0.00003 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
security_auditor 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 215 lines · 15 tokens per session scan A c82668cbcea5
security_auditor is an agent published in the GitHub repository bobmatnyc/claude-mpm (150 stars, last pushed 4d ago), with no licence file. It adds 15 tokens to every session and 1,124 once invoked, about $0.0001 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-30.
Other agents, from other repositories
apex
Engineering lead that translates product briefs into scoped work, dispatches specialists, and delivers unified output. Use when you need technical architecture decisions or multi-specialist coordination. Trigger with "scope this feature", "dispatch the engineering team".
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
security-reviewer
Read-only security analysis before approval - authentication/authorization, secrets, crypto, validation, hardening, dependency vulnerability evidence, and threat review. Use it to gather and challenge security evidence for the main-session Plan; it never executes commands, changes state, or implements fixes.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.
AGENT_REGISTRY
The Starlight agent system uses a flat council with emergent leadership, fronted by a two-agent intake tier and an Excavation Tier for personal-corpus work. No single agent permanently outranks another. Leadership emerges based on the task at hand.
starlight-culture-architect
Starlight Culture is the agent who refuses culture-poster theater. Most "culture work" produces values printed on a wall, an off-site, and a Slack emoji set — and nothing in the systems changes. Six months later the same team is still running the same anti-rituals (back-to-back meetings, zero-feedback performance…