Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add berrzebb/quorum/plugin install 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/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/berrzebb/quorum/perf-analyst"><img src="https://agentmods.dev/badge/agents/berrzebb/quorum/perf-analyst.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.00043 | $0.00353 |
| Opus 5.5 | $0.00017 | $0.00141 |
| Sonnet 5.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 1mo 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.
- 1mo 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 6mo ago), licensed MIT. It adds 43 tokens to every session and 353 once invoked, about $0.0002 per session on Opus 5.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
debugger
Debug issues using MCP-powered discovery.
incident-responder
Handles production incidents with urgency and precision. Use IMMEDIATELY when production issues occur. Coordinates debugging, implements fixes, and documents post-mortems.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
diagnosis-analyst
Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.
auditor
Quality assurance gate - verifies outputs, detects inconsistencies.
harness-doctor
The omp harness inspection + management device. Runs the deterministic health check (harness-check.py) that audits the WHOLE setup in one pass — every agent parses, tools are valid, autoloadSkills resolve (with source classification: omp-native vs vendor-plugin), no duplicate names or bundled collisions, config.yml…