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 fgmacedo/agent-skills --skill removing-dead-codegit clone --depth 1 https://github.com/fgmacedo/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/fgmacedo/agent-skills/removing-dead-code)<a href="https://agentmods.dev/skills/fgmacedo/agent-skills/removing-dead-code"><img src="https://agentmods.dev/badge/skills/fgmacedo/agent-skills/removing-dead-code/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/fgmacedo/agent-skills/removing-dead-code"><img src="https://agentmods.dev/badge/skills/fgmacedo/agent-skills/removing-dead-code.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.00209 | $0.04171 |
| Opus 5.5 | $0.00084 | $0.01668 |
| Sonnet 5.5 | $0.00042 | $0.00834 |
| Haiku 4.5 | $0.00021 | $0.00417 |
Grade A, and why
removing-dead-code 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 5d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Removing Dead Code
Deleting code is cheap to do and cheap to revert only when each deletion is atomic and carries its proof. Static tools produce candidates. What counts as proof depends on the category, and the procedure below is ordered by how much proof each category needs. Never skip ahead: a module that "looks dead" to an analyzer is a candidate, and a candidate is not a deletion.
This file is language-neutral. Tools, exact commands, version pins and the language's own dynamic-reference traps live in one reference per language:
| Language | Reference |
|---|---|
| Python | references/python.md (tool table in references/python-tools.md, production coverage in references/python-production-coverage.md, scripts in scripts/) |
| Other | No reference yet. Follow this file, choose the language's equivalent of each tool category in the "Tool categories" section, and record the tool and version in every commit message. |
RELATED: porting-py2-to-py3 (when the cleanup prepares a Python 2 code base for the port).
Before you start
- Read
references/<language>.mdfor the code base's language. If it does not exist, say so and proceed with the tool categories below. - Run the full test suite and record the result. Freeze the installed dependency set and the lockfile. A project without a lockfile records the installed set and the fact that no lock exists; that is a baseline, not a missing step. Every later step compares against this.
- Start dynamic collection now, even if today's PR only removes imports. Categories 4 and 5 need 30 to 90 days of production data, and the clock only starts when the collector is deployed. When the collector cannot be wired (no common entry point in this repo, no deploy path), the minimum is a tombstone in each suspect with the window end date in the commit message.
- Deploy manifests often live in another repository (container files,
process-manager files, CronJob YAML, CI). Search them there
(
gh search code), or name the check as a merge gate in the commit message. Never assume they are empty because this checkout has none. - Static analysis cannot prove an endpoint, a job, a task or a whole module dead. Read the "Dynamic evidence" section before any claim about those.
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.
- 5d ago First seen · 328 lines · 209 tokens per session scan A 8a68b57e0ec1
removing-dead-code is a skill published in the GitHub repository fgmacedo/agent-skills (10 stars, last pushed 5d ago), licensed MIT. It adds 209 tokens to every session and 4,171 once invoked, about $0.0008 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-13.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…