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/kaeawc/auto-mobile/dead-codenpx skills add kaeawc/auto-mobile --skill dead-codegit clone --depth 1 https://github.com/kaeawc/auto-mobileWhat 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.00037 | $0.00287 |
| Opus 5 | $0.00018 | $0.00143 |
| Sonnet 5 | $0.00007 | $0.00057 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
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 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.
What it actually says
Dead Code
Use this when the user wants dead-code analysis or cleanup.
Workflow
- Start with detection, not deletion.
- For TypeScript, run
bash scripts/detect-dead-code-ts.sh, optionally writing reports toscratch/dead-code/. - Review each candidate in full context before removing it. Unused exports in tooling output are often false positives.
- Check callers, tests, generated code, and dynamic entry points before deleting anything.
- Remove dead code in small batches so regressions are easy to isolate.
- Re-run the detector and the relevant validation after each batch.
Repo Rules
- Prefer repo scripts and
buntasks over ad hoc dead-code tools. - Treat
package.jsondependency findings as suggestions until confirmed. - Do not remove code referenced by reflection, CLI wiring, generated schemas, MCP registration, or platform build files without proof.
- Validate behavior after cleanup with the narrowest relevant commands.
Typical Validation
bun run lintbun run buildbun testbash scripts/validate-bun-test-timings.shwhen test changes may affect the 100ms expectation
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 · 32 lines · 37 tokens per session scan A 4bab5cd3f9b8
dead-code is a skill published in the GitHub repository kaeawc/auto-mobile (45 stars, last pushed 2d ago), licensed Apache-2.0. It adds 37 tokens to every session and 287 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…