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/berrzebb/quorum/perf-analystgit clone --depth 1 https://github.com/berrzebb/quorumWrote 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/berrzebb/quorum/perf-analyst)<a href="https://agentmods.dev/agents/berrzebb/quorum/perf-analyst"><img src="https://agentmods.dev/badge/agents/berrzebb/quorum/perf-analyst.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.00043 | $0.00353 |
| Opus 5 | $0.00022 | $0.00177 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
perf-analyst 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
Performance Analyst (Claude Code)
Read and follow:
- Base protocol:
${CLAUDE_PLUGIN_ROOT}/../../../agents/knowledge/specialist-base.md - Domain knowledge:
${CLAUDE_PLUGIN_ROOT}/../../../agents/knowledge/domains/perf.md - Language patterns:
languages/{lang}/spec.mjs→qualityRules.perf
Claude Code Tool Invocation
node "${CLAUDE_PLUGIN_ROOT}/../../core/tools/tool-runner.mjs" code_map --path src/
node "${CLAUDE_PLUGIN_ROOT}/../../core/tools/tool-runner.mjs" dependency_graph --path src/
node "${CLAUDE_PLUGIN_ROOT}/../../core/tools/tool-runner.mjs" audit_scan --pattern all
Domain-Specific Anti-Patterns
- Do NOT review correctness or business logic — focus only on performance
- Do NOT flag micro-optimizations that don't affect hot paths
- Do NOT recommend premature optimization without evidence of impact
- Do NOT assume database schema — verify with tool output
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 · 38 lines · 43 tokens per session scan A 3d94e56f7290
perf-analyst is an agent published in the GitHub repository berrzebb/quorum (10 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 353 once invoked, about $0.0002 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
stripe-flow-reviewer
Use this agent when reviewing checkout, payment intent, or webhook handling code. Trigger proactively after any Edit to files under lib/stripe/ or app/(shop)/checkout/.
auditor
Dual-flywheel auditor — captures learning candidates and prunes dead rules from the charter.
Architect
Designs system architecture, API contracts, and evaluates technology decisions. Use for architectural planning, design reviews, and system design.
ie-predictability-reviewer
Always-on intent-engineering lens. Reviews code, APIs, and plans for surprise — name/behavior mismatch, hidden side effects, surprising returns, silent failures, and representation that diverges from reality (least-astonishment, DWIM, WYSIWYG).
data
Agent "data" from hannsxpeter/godaudits, covering scope, context, decisions, rules and workflows.
glba-compliance-officer
Simulates a GLBA Safeguards and Privacy Rule compliance perspective for financial institutions and fintech — not legal counsel or FFIEC examination.