Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/varienos/agentic-workflownpx agentmods add commands/varienos/agentic-workflow/deadcode.skeletonWrote 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/varienos/agentic-workflow/deadcode.skeleton)<a href="https://agentmods.dev/commands/varienos/agentic-workflow/deadcode.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/deadcode.skeleton/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/varienos/agentic-workflow/deadcode.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/deadcode.skeleton.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.03052 |
| Opus 5.5 | $0.00000 | $0.01221 |
| Sonnet 5.5 | $0.00000 | $0.00610 |
| Haiku 4.5 | $0.00000 | $0.00305 |
Grade A, and why
deadcode.skeleton 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 22d 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead Code Hunter — Unused Code Detection and Cleanup
Detects unused code, exports, functions, and files based on security levels, cleans up after verification.
Usage:
/deadcode [directory]
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.
- 22d ago Changed · -24 lines d3c18f268f8c
- 1mo ago First seen · 413 lines · 0 tokens per session scan A 65874c8962ac
deadcode.skeleton is a command published in the GitHub repository varienos/agentic-workflow (59 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,052 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-30.
Other commands, from other repositories
quality-review
Run the 3-agent quality review (simplifier + adversarial-reviewer + chaos-engineer) against a plan, file, or proposal.
architecture-review
Architecture + code-health audit — module boundaries, then fallow on TS/JS — and a task per finding.
polish
You are polishing code that was just written. This runs a two-phase quality pass — review then simplify — and auto-applies all changes. The user sees a final report of everything that changed.
gh-resolve-pr
Fix CI and review findings on a GitHub PR, then report readiness.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
review
A command for reviewing code with security checks and a check for compliance with MX tags. The available description does not explain what MX tags are.