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/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/performance-auditor)<a href="https://agentmods.dev/agents/charlesjones-dev/claude-code-plugins-dev/performance-auditor"><img src="https://agentmods.dev/badge/agents/charlesjones-dev/claude-code-plugins-dev/performance-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/charlesjones-dev/claude-code-plugins-dev/performance-auditor"><img src="https://agentmods.dev/badge/agents/charlesjones-dev/claude-code-plugins-dev/performance-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.00027 | $0.00122 |
| Opus 5.5 | $0.00011 | $0.00049 |
| Sonnet 5.5 | $0.00005 | $0.00024 |
| Haiku 4.5 | $0.00003 | $0.00012 |
Grade A, and why
performance-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 10d 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
Load the performance-audit skill and follow its methodology and provide a structured report using the performance-audit skill's defined template.
Focus on identifying and optimizing:
- Performance bottlenecks in code execution and database queries
- Caching opportunities and strategies
- Frontend asset delivery and rendering performance
- Backend query optimization and resource management
- Memory usage and potential memory leaks
- Infrastructure and scaling considerations
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.
- 10d ago Changed · -5 tokens per session cca31f99bae7
- 1mo ago First seen · 17 lines · 32 tokens per session scan A de134d5be721
performance-auditor is an agent published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 6d ago), licensed MIT. It adds 27 tokens to every session and 122 once invoked, about $0.0001 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-30.
Other agents, from other repositories
git-investigator
Code archaeology expert. Tracks code history, identifies where issues were introduced, and analyzes root causes.
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
git-historian
Use this agent for git archaeology, when the user asks "why does this code exist", "when did this break", "what introduced this behavior", mentions "git blame", "git bisect", "pickaxe", "regression", "who changed this", or "find the commit that". Examples.
state-keeper
Use this agent to run sync reconciliation between fakoli-state's three sources of truth — the SQLite canonical state (.fakoli-state/state.db), the filesystem (packets/, .evidence-buffer/, worktrees), and git (branches, commits, claims). It surfaces drift as structured discrepancy reports — orphan branches (claimed…
qa-lead
The QA Lead owns test strategy, bug triage, release quality gates, and testing process design. Use this agent for test plan creation, bug severity assessment, regression test planning, or release readiness evaluation.
code-archaeologist
Diagnostic specialist — traces WHEN a bug was introduced and WHY the code was written this way, using git history. Read-only investigator. Does NOT write fixes. Spawned by /brigade:bug-council or /brigade:fix on 3+ failed fix attempts.