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 melodic-software/claude-code-plugins/plugin install code-metricsWrote 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/skills/melodic-software/claude-code-plugins/audit-suppressions)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/audit-suppressions"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/audit-suppressions/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/skills/melodic-software/claude-code-plugins/audit-suppressions"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/audit-suppressions.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.00160 | $0.02906 |
| Opus 5.5 | $0.00064 | $0.01162 |
| Sonnet 5.5 | $0.00032 | $0.00581 |
| Haiku 4.5 | $0.00016 | $0.00291 |
Grade A, and why
audit-suppressions 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 4d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
Current branch: !git branch --show-current 2>/dev/null || echo "unknown"
Purpose
A suppression turns a linter or type checker off for one line, one block or one file. Each one is
a decision someone made once; this skill lists them so a reader can see how many there are, which
explain themselves, and which switch off a rule the team counts as correctness rather than style.
It reports and stops: no pass or fail, and the report carries no severity (a --findings file
carries the tier its rule's row sets, below). Whether a suppression should go is the reader's call.
A suppression is justified when its line carries a reason and, for a tool whose syntax can name
a rule, at least one rule id. TypeScript's @ts-ignore, @ts-expect-error and @ts-nocheck
cannot name an error, so a reason alone justifies them. Where a tool has a reason slot of its own,
the text there is the reason (ESLint and RuboCop after --, a Justification argument in C# and
PowerShell); otherwise a further comment on the same line is (a TypeScript directive's trailing
text, a second <!-- --> after a markdownlint directive, a // comment after @SuppressWarnings,
a second # comment after a Python or shell pragma).
Only real comments, pragmas and attributes count. A marker inside a string literal, a Markdown code span or a fenced code block in a Markdown file is not a suppression.
Run it
"${CLAUDE_SKILL_DIR}/scripts/audit-suppressions.sh" # lines the commits since the merge-base add
"${CLAUDE_SKILL_DIR}/scripts/audit-suppressions.sh" --base release/2.0 # the merge-base with another branch
"${CLAUDE_SKILL_DIR}/scripts/audit-suppressions.sh" --all # every suppression in the tree
"${CLAUDE_SKILL_DIR}/scripts/audit-suppressions.sh" src/ tools/build.sh # explicit paths, whole files
"${CLAUDE_SKILL_DIR}/scripts/audit-suppressions.sh" --json --all # the document instead of markdown
"${CLAUDE_SKILL_DIR}/scripts/audit-suppressions.sh" --findings # the report plus a findings file for /review:fanout fix
What ships with it
4 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.
- 4d ago First seen · 175 lines · 160 tokens per session scan A eb946c7ff9e2
audit-suppressions is a skill published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. It adds 160 tokens to every session and 2,906 once invoked, about $0.0006 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-10-12.
Other skills, from other repositories
refactor-decompose-function
For long functions: break into smaller pieces, extract helper functions, reduce nesting, improve testability and readability.
pr-analyzing
Use this skill when the user asks to analyze a specific GitHub pull request, review a PR's architectural impact, assess what changed in a PR and why it matters, or research the code relationships affected by a PR — example triggers like "analyze PR.
find-shortest-path
For pathfinding and search: shortest path, maze solving, game AI, route planning, graph traversal, BFS/DFS, Dijkstra, A problems.
catch-expected-errors
For iteration with errors: catch exceptions during exploration, skip invalid cases, continue to next attempt.
rust-coding-standards
Rust coding standards, documentation authoring, content workflows, and quality patterns for systemprompt.io development.
visual-design-system
World-class visual design system standards — OKLCH color science, fluid typography, elevation hierarchy, branded asymmetric corners, and dark mode implementation.