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/mathisk2095/jko-claude-plugins/dead-code-expertnpx skills add mathisk2095/jko-claude-plugins --skill dead-code-expertgit clone --depth 1 https://github.com/mathisk2095/jko-claude-pluginsWrote 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/mathisk2095/jko-claude-plugins/dead-code-expert)<a href="https://agentmods.dev/skills/mathisk2095/jko-claude-plugins/dead-code-expert"><img src="https://agentmods.dev/badge/skills/mathisk2095/jko-claude-plugins/dead-code-expert.svg" alt="Measured on agentmods" 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 | $0.00132 | $0.01466 |
| Opus 5 | $0.00066 | $0.00733 |
| Sonnet 5 | $0.00026 | $0.00293 |
| Haiku 4.5 | $0.00013 | $0.00147 |
Grade A, and why
dead-code-expert 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead Code Expert
Find and eliminate dead code, duplicate implementations, and unnecessary complexity across any programming language. Every finding explains WHY the code is dead and the concrete cost of keeping it (cognitive overhead, build time, misleading developers, masking bugs).
How to Think About Dead Code
Before flagging anything, identify which category it belongs to:
- Layer 1 -- Certainly Dead: Unreachable code after return/break/throw, unused private functions, unused local variables, imports with zero references. Safe to remove immediately.
- Layer 2 -- Probably Dead: Exported functions with no callers in the project, commented-out code blocks,
#[allow(dead_code)]/// eslint-disable unusedsuppressions, permanently-off feature flags. Verify before removing. - Layer 3 -- Suspiciously Alive: Code that LOOKS dead but may be used via reflection, serialization, framework magic, dynamic dispatch, or public API surface. Investigate before touching. → Consult false-positives reference for the full 10-category checklist and scoring framework.
When dead code is found, reframe it as a design question:
| Dead Code Pattern | Don't Just Say | Ask Instead |
|---|---|---|
| Unused function | "Delete it" | Why was it written? Is there a missing caller? |
| Duplicate implementation | "Remove one" | Which is canonical? Why did duplication happen? |
| Commented-out block | "Delete it" | Is there in-progress work? Check git blame. |
| Unused abstraction layer | "Inline it" | Was it speculative generality? |
| Dead feature flag | "Remove the branch" | Is there a deprecation process to follow? |
Detection Process
When scanning for dead code, work through these categories in order.
-
Unused Imports -- Imports/includes/requires with no reference in file. → Consult grep patterns for per-language detection.
-
Unused Variables & Parameters -- Assigned but never read (dead stores).
-
Unused Functions & Methods -- Defined but never called.
-
Unused Classes & Types -- Defined but never instantiated or referenced. → Consult detection catalog for categories 2-6 with per-language tools.
What ships with it
8 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 · 100 lines · 132 tokens per session scan A 2782ba85abe4
dead-code-expert is a skill published in the GitHub repository mathisk2095/jko-claude-plugins (3 stars, last pushed 5d ago), licensed MIT. It adds 132 tokens to every session and 1,466 once invoked, about $0.0007 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-31.
Other skills, from other repositories
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
seam-probe
This skill should be used when testing or debugging an embedded-runtime boundary exposed through a dynamically loaded C-ABI library or Unix-domain socket, including requests to inspect exports, exercise FFI callbacks, send framed messages, reproduce seam crashes or hangs, fuzz a boundary, or correlate probe output…
electron-playwright-validator
This skill should be used when a user asks to launch, inspect, automate, test, validate, or debug an Electron desktop UI through Playwright/CDP, including blank renderers, runtime import failures, accessibility snapshots, layout defects, click-through flows, or post-change checks. Not for native macOS or mobile apps…
mobile-flows-maestro
This skill should be used when Maestro is explicitly requested or already present and the task is to author, run, or debug iOS/Android Maestro flows; use Maestro MCP; or handle Maestro selectors, system UI, permissions, Keychain, JavaScript, waits, device state, flakiness, or CI. Evidence includes a .maestro directory…
validate-mobile
Run a Maestro flow on an explicitly selected iOS or Android device and report behavioral evidence.
validate-api
Run the project's Hurl scenarios with an OIDC access token passed as a secret variable.