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.
git clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/commands/kensaurus/cursor-kenji/deadcode-plan)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/deadcode-plan"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/deadcode-plan/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/commands/kensaurus/cursor-kenji/deadcode-plan"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/deadcode-plan.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.00017 | $0.00252 |
| Opus 5 | $0.00009 | $0.00126 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
deadcode-plan 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 today.
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 Plan
Run the plan-dead-code skill: author knip.json before trusting any
output, resolve every configuration hint, baseline both --production and
default runs, then count the surfaces Knip cannot see — unused locals,
duplication, debug residue, suppression debt, orphan assets, env drift,
dead schema. Audit and plan only — delete no file, export, dependency,
asset, or row until the plan is approved.
On a first run most findings are misconfiguration, not dead code. Report
the before/after finding counts so the difference is visible, and mark
anything reached dynamically, generated, or deliberately public as
keep-* rather than guessing kill.
Emit plan-dead-code.md: baseline table, keep/kill list with evidence and
risk, phased burndown, and the --max-issues ratchet proposal. After
approval, execute with housekeep-dead-code.
The full playbook lives in the plan-dead-code skill.
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.
- today First seen · 25 lines · 17 tokens per session scan A 1221aebb6eb7
deadcode-plan is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 252 once invoked, about $0.0001 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-09-11.
Other commands, from other repositories
learn
Learn about Task Master capabilities through interactive exploration.
fix-dependencies
Automatically fix dependency issues found during validation.
smart-workflow
Execute an intelligent workflow based on current project state and recent commands.
validate-dependencies
Validate all task dependencies for issues.
expand-all-tasks
Expand all pending tasks that need subtasks.
to-done
Command "to-done" from eyaltoledano/claude-task-master, covering completing a task, pre-completion checks, execution, post-completion actions and celebration & learning.