Repowise is a codebase intelligence tool that indexes source code, dependencies, history, tests, documentation, and architectural decisions to answer questions about software projects. It helps developers and coding agents understand systems, assess change impact, identify dead or risky code, and improve code health. Its catalogue add-ons extend agent workflows for using Repowise.
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 skills add repowise-dev/repowise --skill dead-code-cleanupgit clone --depth 1 https://github.com/repowise-dev/repowiseWrote 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/repowise-dev/repowise/dead-code-cleanup)<a href="https://agentmods.dev/skills/repowise-dev/repowise/dead-code-cleanup"><img src="https://agentmods.dev/badge/skills/repowise-dev/repowise/dead-code-cleanup/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/repowise-dev/repowise/dead-code-cleanup"><img src="https://agentmods.dev/badge/skills/repowise-dev/repowise/dead-code-cleanup.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.00059 | $0.00492 |
| Opus 5.5 | $0.00024 | $0.00197 |
| Sonnet 5.5 | $0.00012 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
dead-code-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 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 43 lines · 59 tokens per session scan A 94434a347b4e
dead-code-cleanup is a skill published in the GitHub repository repowise-dev/repowise (7,882 stars, last pushed today), licensed AGPL-3.0. It adds 59 tokens to every session and 492 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
scip-integrity-audit
Investigate whether a feature fulfills its promised behavior through live consumers. Find partial implementations, decorative checks, ineffective parser migrations, competing implementations, misleading results, and tests validating their own assumptions.
scip-query
Use code relationships, module structure, quality findings and change impact to plan and review changes alongside ordinary source-reading tools.
scip-explore
Understand existing implementation paths, callers, consumers and dependencies with targeted relationship queries and ordinary source reads.
scip-setup
Install, diagnose, index, watch, repair, or clean up scip-query for a repository. Use for setup, freshness, cache ownership, worktrees, watcher behavior, and operational failures—not ordinary code exploration.
x-ray
Deep codebase exploration using semantic search and relationship mapping. Use when you need to understand the current codebase.
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…