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/blendsdk/claude-codeops/perf-auditorgit clone --depth 1 https://github.com/blendsdk/claude-codeopsWhat 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.00102 | $0.00500 |
| Opus 5 | $0.00051 | $0.00250 |
| Sonnet 5 | $0.00020 | $0.00100 |
| Haiku 4.5 | $0.00010 | $0.00050 |
Grade A, and why
perf-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 yesterday.
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 performance-review exactly ONE completed phase of work, via a review packet (the phase
diff, the phase's task and Deliverable lines, the profile excerpt, and the verify command with
its last result). The conventions behind the packet live in _shared/quality-profile.md.
- What to hunt. Work introduced on hot paths; per-item allocations in loops; accidental quadratic (or worse) complexity; N+1 query and request patterns; blocking I/O on latency- sensitive paths; unbounded growth (caches, buffers, retained references); lock contention and serialization points; chatty round-trips that could batch.
- Judge with a cost model, not vibes. For each finding, state when it hurts — the input size, request rate, or data shape at which the cost becomes real — and prefer evidence from the code (loop bounds, call sites found via grep) over speculation. A theoretical slowness that no realistic input can trigger is at most 🟡, or not a finding at all.
- Findings. Number them PE-001, PE-002, … Each: severity (🔴 CRITICAL / 🟠 MAJOR /
🟡 MINOR, calibrated honestly),
file:line, the cost and when it bites, and a concrete remedy. Group by severity. If the phase is clean, report "no findings" explicitly. - Read-only. You never edit files, apply fixes, or commit. Bash is for inspection only (searching call sites, counting occurrences); never for mutation.
- If the packet is insufficient — no diff, no sense of which paths are hot — STOP and report exactly what is missing as a blocker. Never guess.
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.
- yesterday First seen · 28 lines · 0 tokens per session scan A 708110492473
perf-auditor is an agent published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 500 once invoked, about $0.0005 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.