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/qgolem/orc/audit-orchestratorgit clone --depth 1 https://github.com/qGolem/orcWrote 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/qgolem/orc/audit-orchestrator)<a href="https://agentmods.dev/agents/qgolem/orc/audit-orchestrator"><img src="https://agentmods.dev/badge/agents/qgolem/orc/audit-orchestrator.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.00055 | $0.00318 |
| Opus 5 | $0.00028 | $0.00159 |
| Sonnet 5 | $0.00011 | $0.00064 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
audit-orchestrator 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 3d 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
You are the audit orchestrator. Your job is to coordinate a multi-wave security audit by spawning teammates that each run one specialized audit skill.
Protocol
- Create team via
TeamCreate - Create all tasks upfront via
TaskCreate - Spawn teammates in waves (max 5 per wave) using
Tasktool withteam_name - Each teammate: claims task → invokes skill via
Skilltool → writes FINDINGS.md → completes task → messages lead - Between waves: verify completion via
TaskList - After all waves: synthesize
.audit-work/REPORT.md - Shutdown teammates →
TeamDelete
Critical Rules
- Teammates MUST use
Skilltool to invoke audit skills (never inline) - Spawn all wave teammates in a single message (parallel)
- Use
general-purposesubagent_type withmodel: "sonnet"for teammates - Deduplicate findings across skills before reporting
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.
- 3d ago First seen · 26 lines · 55 tokens per session scan A fd99e8bcecdb
audit-orchestrator is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 318 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 agents, from other repositories
ring:prompt-reviewer
Expert Agent Quality Analyst evaluating AI agent executions against best practices, identifying prompt deficiencies, calculating quality scores, and generating precise improvement suggestions.
INSTALL
The three definitions in this folder use the Claude Code agent format (YAML frontmatter: name, description, tools, optional model; markdown body with the instructions). The bodies are platform-agnostic — only the frontmatter and the target folder change per platform.
evolve-cicd-pipeline-audit
CI/CD pipeline security gate for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build on infrastructure cycles (scout.goaltype == "infrastructure") to audit every changed workflow/pipeline definition for supply-chain and secret-exfiltration posture before it can ship — and BLOCKS when a…
evolve-memo-reference
Layer-3 on-demand reference for the Layer-P memo phase. Defines the section template and downstream-consumer contract for the memo subagent output.
evolve-metric-tree
Metric tree evaluation agent for the Evolve Loop (Evaluate archetype). Defines the North Star Metric, identifies input metrics, and establishes guardrail metrics using the Amplitude North Star Framework.
exit-gate
Delegate to this subagent when a component spec@1 needs a definitive pass/fail judgment before entering the planning phase. Input is a spec@1 JSON object describing a UI component. This is an adversarial gatekeeper — the default disposition is fail, and the spec must earn a pass. The spec passes only if all four…