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/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/qa-perf)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/qa-perf"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/qa-perf/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/commands/christopherlouet/claude-base/qa-perf"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/qa-perf.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.00000 | $0.00376 |
| Opus 5 | $0.00000 | $0.00188 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
qa-perf 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 6d 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
PERF Agent (Performance)
Performance analysis and optimization.
Target
$ARGUMENTS
Objective
Measure, identify bottlenecks and optimize performance following a data-driven approach (profiling before optimization).
Workflow
- Measure the performance baseline (time, memory, CPU)
- Identify bottlenecks (code, frontend, backend)
- Profile with the appropriate tools (DevTools, Lighthouse, autocannon)
- Check Core Web Vitals (LCP, FID, CLS, TTFB, INP)
- Propose optimizations by priority (algorithm > cache > lazy loading)
- Measure after optimization to validate impact
Expected output
Baseline
- Metric 1: [initial value]
- Metric 2: [initial value]
Identified bottlenecks
| Location | Problem | Estimated impact |
|---|
Proposed optimizations
- [Optimization 1] - Estimated gain: [X%]
- [Optimization 2] - Estimated gain: [X%]
Results after optimization
- Metric 1: [before] -> [after] ([X% improvement])
Related agents
| Agent | When to use it |
|---|---|
/ops:ops-monitoring |
Monitor performance in prod |
/ops:ops-database |
Optimize DB queries |
/qa:qa-audit |
Full audit (includes perf) |
/growth:growth-seo |
Core Web Vitals for SEO |
IMPORTANT: "Premature optimization is the root of all evil" - Knuth. Optimize only what is measured as slow.
YOU MUST measure before and after each optimization to validate the impact.
NEVER optimize without prior profiling - identify the real bottleneck.
Think hard about the cost/benefit ratio of each optimization.
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.
- 6d ago First seen · 56 lines · 0 tokens per session scan A 54e0cf4a85d5
qa-perf is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 376 tokens. 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-09-03.
Other commands, from other repositories
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
debug
Run a 4-phase systematic debugging investigation before proposing any fix. Iron Law — NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Produces a .orchestrator/debug/ artifact the fixer agent must reference.
health-check
Run diagnostics on Claude Code toolkit configuration and status.
quick-fix
Run the implement→review subagent loop without the planning phase — for straightforward fixes with a known cause and one obvious approach, regardless of how many files the change spreads across. Skips the spec gate, worktree gate, and finalize ceremony (implementation log, docs, signals) that /subagent-implementation…
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.