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 skills add adityaarakeri/senior-agent-skills --skill dead-code-auditgit clone --depth 1 https://github.com/adityaarakeri/senior-agent-skillsWrote 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/adityaarakeri/senior-agent-skills/dead-code-audit)<a href="https://agentmods.dev/skills/adityaarakeri/senior-agent-skills/dead-code-audit"><img src="https://agentmods.dev/badge/skills/adityaarakeri/senior-agent-skills/dead-code-audit/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/adityaarakeri/senior-agent-skills/dead-code-audit"><img src="https://agentmods.dev/badge/skills/adityaarakeri/senior-agent-skills/dead-code-audit.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.02215 |
| Opus 5 | $0.00000 | $0.01107 |
| Sonnet 5 | $0.00000 | $0.00443 |
| Haiku 4.5 | $0.00000 | $0.00221 |
Grade A, and why
dead-code-audit 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 9d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
10 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.
- README.md 2.7 KB
- references/configs-ci-hygiene.md 4.0 KB
- references/go-rust-java.md 2.2 KB
- references/javascript.md 2.2 KB
- references/manual-analysis.md 1.9 KB
- references/python.md 1.9 KB
- references/safe-removal.md 4.7 KB
- scripts/hygiene_scan.py 7.2 KB runs code
- scripts/size_repo.py 5.0 KB runs code
- scripts/symbol_index.py 5.0 KB runs code
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.
- 9d ago First seen · 172 lines · 0 tokens per session scan A 85045d3d37fb
dead-code-audit is a skill published in the GitHub repository adityaarakeri/senior-agent-skills (1 stars, last pushed 22d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 2,215 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-08-31.
Other skills, from other repositories
offensive-bug-identification
Systematic bug identification methodology: source code review patterns, black-box testing strategies, taint analysis, dangerous function hunting, data flow tracing, and automated scanning setup. Use for code audits, bug bounty triage, or building vulnerability identification pipelines.
triage-issue
Verify an issue, persisted audit finding, or unresolved review finding against current code, classify it, and write only the contracted forge/ledger outcome. Supports independent batches and an immediate-fix review-finding route. Triggers: "triage-issue", "triage issue N", "triage this finding", "is this trigger met".
dredge
When something goes wrong during a build — including when the report can't be reproduced at all — diagnose what type of failure it is before deciding how to respond. Targeted fix, hard reset, full rethink, or a reproduction gap — the right response depends on the right diagnosis.
python-performance-optimization
Profile and optimize Python code using cProfile, memory profilers, and performance best practices.
prove-checks
Prove a passing check was capable of failing before recording it as evidence. Use when a test, CI job, build-and-diff, smoke test or rehearsal comes back green and that green is about to be treated as proof - especially when the check depends on a setup mutation (a sed/awk rewrite, an env var, a secret, a fixture…
logging-patterns
Logging conventions -- level usage, formatting style, structured output.