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 skills/melodic-software/claude-code-plugins/audit-performancenpx skills add melodic-software/claude-code-plugins --skill audit-performancegit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWhat 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.00325 | $0.03371 |
| Opus 5 | $0.00162 | $0.01685 |
| Sonnet 5 | $0.00065 | $0.00674 |
| Haiku 4.5 | $0.00032 | $0.00337 |
Grade A, and why
audit-performance 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
"It was slow, so I deleted everything and reinstalled" destroys the evidence and confounds the fix: a reinstall crosses version upgrades, so nobody learns whether accumulated state, a version regression, or component bloat was the cause. This skill is the five-minute capture that runs while it is slow, so the diagnosis rests on measurements instead of a nuked crime scene.
It deliberately answers "what is true right now" and refuses "so delete X". Remediation routes
out (see the boundary table). The engine's own phase timings are first-class evidence: a census
walk that takes minutes IS the cost the product's retention sweep pays on that tree; a
claude --version probe that takes ten seconds is itself a finding.
Scope boundary
| Question | Owner |
|---|---|
| Why is Claude Code slow right now? | this skill |
| What exactly is in the install tree, and is anything stale? | /claude-ops:audit-install-state |
| Which plugins are enabled at which scope, and is the fleet current? | /claude-ops:plugins audit |
| Is this a known upstream bug? | /claude-ops:known-issues (compose: search the symptoms this report surfaces) |
| Delete a genuinely unmanaged leftover | /disk-hygiene:clean |
Shed one project's ~/.claude.json state |
claude project purge <path> |
Never read
.credentials.json, daemon/*.key, ide/*.lock bodies, the values inside ~/.claude.json, and
the contents of history.jsonl and transcript files. The engine's content-read allowlist is four
non-secret config files: settings.json, .last-cleanup, a plugin's hooks/hooks.json, and
plugins/installed_plugins.json. Everything else is stat-only. Name, size, mtime. The allowlist
is enforced in read_json, which raises rather than reading a file it does not name, so the
prose and the code cannot drift apart.
The last two entries are new, and they are what makes hook enumeration possible: a hook manifest holds an event, a matcher, and a command string, and the installed-plugins manifest holds install paths. Neither carries credential material. Nothing else was opened to add them.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 198 lines · 325 tokens per session scan A dc1ae1724e15
audit-performance is a skill published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed 2d ago), licensed MIT. It adds 325 tokens to every session and 3,371 once invoked, about $0.0016 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-30.
Other skills, from other repositories
deep-research
Conducts iterative deep research on any topic using web search, progressive exploration, and structured synthesis. Use when asked for comprehensive research, deep investigation, thorough analysis, or multi-source exploration of any topic. Triggers: research, investigate, deep dive, comprehensive analysis, explore…
error-ux
Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code. Triggers: error messages, user experience, error handling, exception messages, validation errors.
adversarial-patterns
Library of realistic adversarial attack vectors and anti-patterns to avoid. Contains examples of valid attacks and subtle gaming patterns to reject.
documentation-testing
Provides heuristics for identifying incomplete or broken documentation. Use when validating README setup instructions, testing onboarding flows, or auditing documentation quality. Triggers: docs, readme, onboarding, setup validation, documentation audit.
adversarial-analysis
Analyze code to identify explicit contracts, implicit usage patterns, and realistic boundary conditions. Contains concrete formulas for calculating input realism limits. Use before generating adversarial tests.
propagate-then-search
For constraint problems: eliminate impossibilities before guessing, reduce search space through inference, fail fast on contradictions.