Borrowing it
Nothing to install: this file belongs to statecrafting/spec-spine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/statecrafting/spec-spine/main/.claude/skills/cleanup/SKILL.mdgit clone --depth 1 https://github.com/statecrafting/spec-spineWrote 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/statecrafting/spec-spine/cleanup)<a href="https://agentmods.dev/skills/statecrafting/spec-spine/cleanup"><img src="https://agentmods.dev/badge/skills/statecrafting/spec-spine/cleanup.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.1 | $0.00035 | $0.01161 |
| Opus 5 | $0.00017 | $0.00580 |
| Sonnet 5 | $0.00007 | $0.00232 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
cleanup 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 yesterday.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cleanup: Cleanup Analysis
Purpose
Spawn one analyzer sub-agent that runs dead-code and duplicate-code
detection across the source surface AGENTS.md or CLAUDE.md names,
reads each finding in context, and returns a structured report. Optional
detectors are used when available and skipped visibly when not.
Usage
/cleanup # dead code + duplicates
/cleanup dead-code
/cleanup duplicates
Execution
Step 1: parse arguments
$ARGUMENTS selects detectors; default is both. Valid tokens: dead-code,
duplicates.
Step 2: spawn the analyzer
Use the Agent tool (type explorer, read-only) with this prompt, passing
the selected detectors and the source surface:
You are a cleanup analyzer. Analyze and report; change nothing.
Detectors to run: [selected] Source surface: [directories]
A. Dead code. Per language present, prefer the stack's own detector and fall back visibly:
| Language | Detector | Fallback |
|---|---|---|
| Rust | cargo clippy --workspace --all-targets --locked -- -W dead_code -W unused, cargo udeps (nightly) |
each crate's [dependencies] against its use lines; a file under src/ no mod or use path references |
| TypeScript | npx --no-install knip --no-exit-code |
an exported symbol no import references |
| Python | vulture |
a module nothing imports |
| Go | go vet ./..., staticcheck ./... |
an unexported identifier with one definition and no use |
Count the linter's unused findings separately from orphan files.
B. Duplicates. A duplicate detector if installed (jscpd, simian,
cpd); otherwise surface near-identical public function signatures
across the surface (grep -rn "^pub fn\|^export function\|^def \|^func "
then sort | uniq -d). Treat results as hints.
C. Investigate every finding by reading the source before categorizing.
D. Categorize.
Keep (false positives): anything under the derived directory (compiler output); generated code; trait or interface implementations reached only through dynamic dispatch (the seams the project's rules name); public API of a library consumed by another package; test fixtures and builders; fuzz targets; workflow and hook scripts; entry points and registries; any never-touch artefact the path-scoped rules name.
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.
- yesterday First seen · 137 lines · 35 tokens per session scan A 1e4cbd92c7d9
cleanup is a skill published in the GitHub repository statecrafting/spec-spine (10 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 1,161 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-09-07.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.