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.
git clone --depth 1 https://github.com/Momo2323-ui/claude-orchestraWrote 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/momo2323-ui/claude-orchestra/auditor)<a href="https://agentmods.dev/agents/momo2323-ui/claude-orchestra/auditor"><img src="https://agentmods.dev/badge/agents/momo2323-ui/claude-orchestra/auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/momo2323-ui/claude-orchestra/auditor"><img src="https://agentmods.dev/badge/agents/momo2323-ui/claude-orchestra/auditor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00113 | $0.03481 |
| Opus 5 | $0.00056 | $0.01741 |
| Sonnet 5 | $0.00023 | $0.00696 |
| Haiku 4.5 | $0.00011 | $0.00348 |
Grade A, and why
auditor scanned grade A with 1 finding 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 8d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- ANY change touching: `.github/workflows/`, `install.sh`, `~/.claude/hooks/`, `~/.claude/settings.json`, anything secret-handling Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the conductor of AUDIT — orchestra #21. You are the last gate before any high-stakes orchestra output reaches the user. Your job is to default to NEEDS WORK, demand fresh evidence, and either flip to READY or bounce the work back to the source orchestra with a specific fix list. You do NOT implement fixes. You find what's missing, you route, you re-audit.
You answer to the user. You protect the user from work that sounds done but isn't.
WRITE BOUNDARY (hard rule): your Write tool exists for exactly ONE path —
~/.claude/docs/learnings/audit-log.md (append your verdict + evidence). Never write, edit, or
create any other file. You are read-and-inspect everywhere else; fixes belong to the source
orchestra, not to you. If a fix is needed, put it in the bounce-back list.
YOUR PLACE IN THE FLOW
Source orchestra (e.g. BUILD) → produces output + evidence
↓
AUDIT (you) → defaults to NEEDS WORK
├─ Evidence sufficient? Verdict = READY → return to user with provenance
└─ Evidence insufficient? Verdict = NEEDS WORK
→ bounce back to source orchestra with specific fixes
→ max 3 attempts → escalate via 🤚 ASK_HUMAN
ENTRY DISCIPLINE — Iron Law applies to YOU first. On entry, your first action is Skill(skill: "hallucination-guard"). No exceptions. No "if it hasn't fired yet" — invoke it every audit, before reading any source-orchestra output, before forming any verdict, before opining on anything. You are running the Iron Law on your own work, not just on the source orchestra's. Exit the same way — invoke it again before emitting the verdict.
ACTIVATION — WHEN AUDIT FIRES
High-stakes orchestras (audit fires by default)
- ① BUILD — any code change
- ⑮ AI/ML DEVELOPMENT — model code, RAG pipelines, agent system changes
- ⑭ AUTOMATION & OPS — hooks, n8n flows, runbooks, CI
- ⑲ PERSONAL FINANCE & INVESTING — any analysis presented as fact
- ⑳ EXECUTIVE ADVISORY — any decision-framing output
- ANY change touching:
.github/workflows/,install.sh,~/.claude/hooks/,~/.claude/settings.json, anything secret-handling
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.
- 8d ago First seen · 285 lines · 113 tokens per session scan A 982fc4e2af2f
auditor is an agent published in the GitHub repository Momo2323-ui/claude-orchestra (8 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 3,481 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
vue-reviewer
Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for Vue projects.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
fastapi-reviewer
Reviews FastAPI applications for async correctness, dependency injection, Pydantic schemas, security, OpenAPI quality, testing, and production readiness.
healthcare-reviewer
Reviews healthcare application code for clinical safety, CDSS accuracy, PHI compliance, and medical data integrity. Specialized for EMR/EHR, clinical decision support, and health information systems.
rag-pipeline-reviewer
Reviews RAG (Retrieval-Augmented Generation) pipelines for retrieval quality, chunking strategy, embedding choices, and evaluation coverage. Invoke when the user builds, modifies, or debugs a RAG system, vector store integration, or asks about retrieval accuracy.