Borrowing it
Nothing to install: this file belongs to future-architect/uzomuzo-oss. 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/future-architect/uzomuzo-oss/main/.claude/skills/deadcode/SKILL.mdgit clone --depth 1 https://github.com/future-architect/uzomuzo-ossWrote 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/future-architect/uzomuzo-oss/deadcode)<a href="https://agentmods.dev/skills/future-architect/uzomuzo-oss/deadcode"><img src="https://agentmods.dev/badge/skills/future-architect/uzomuzo-oss/deadcode/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/skills/future-architect/uzomuzo-oss/deadcode"><img src="https://agentmods.dev/badge/skills/future-architect/uzomuzo-oss/deadcode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00230 |
| Opus 5.5 | $0.00011 | $0.00092 |
| Sonnet 5.5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
deadcode 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 1mo 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
/deadcode — Dead Code Detection & Removal
Full specification: See
.github/prompts/deadcode.prompt.mdfor the complete detection procedure, classification rules, output format, and safety rules.
Quick Reference
- Audit mode (default):
/deadcode— detect and report only - Fix mode:
/deadcode fix— detect, remove SAFE items, confirm CAREFUL items - Scoped:
/deadcode internal/infrastructure/— limit to a package path - Detection:
go vet,go build,deadcode ./...,go mod tidy -v, manual grep - Classify: SAFE / CAREFUL / RISKY
- After each removal batch:
go build ./... && go test ./... && go vet ./... - Never auto-remove
pkg/uzomuzo/public API or reflect/generate/linkname targets
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.
- 1mo ago First seen · 20 lines · 27 tokens per session scan A 2cb934dcd5b1
deadcode is a skill published in the GitHub repository future-architect/uzomuzo-oss (42 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 230 once invoked, about $0.0001 per session on Opus 5.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-01.
Other skills, from other repositories
test-fix
Diagnose and minimally fix a failing test, then re-run.
debugging
Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work', 'X is broken', 'something's wrong', 'getting an error', 'exception in', 'stopped working', 'regression', 'crash', 'hang', 'flaky test', 'intermittent failure', or when user pastes a stack…
ralphctl-debugging-and-error-recovery
Systematic root-cause debugging. Use when tests fail, builds break, something that worked before broke, or behaviour does not match expectations — when you need to figure out what broke and why. Follow stop-the-line → reproduce → localize → reduce → root-cause → guard-with-regression-test → verify, not guessing; the…
regression-test-gen
Suggest regression coverage for changed stack behavior.
fix-bug
Investigates and fixes a reported bug. Reads relevant code, identifies the root cause, proposes a fix, and adds or updates tests to prevent regression. Invoked when the user describes unexpected behavior, an error, a crash, or a failing test.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…