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/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/dead-code)<a href="https://agentmods.dev/commands/googilyboogily/googilyboogily-claude-power-tools/dead-code"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/dead-code/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/googilyboogily/googilyboogily-claude-power-tools/dead-code"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/dead-code.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.00023 | $0.03140 |
| Opus 5 | $0.00012 | $0.01570 |
| Sonnet 5 | $0.00005 | $0.00628 |
| Haiku 4.5 | $0.00002 | $0.00314 |
Grade A, and why
dead-code 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 11d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead Code Finder
Project Detection
!ls package.json tsconfig.json pyproject.toml setup.py setup.cfg requirements.txt Cargo.toml go.mod go.sum Gemfile pom.xml build.gradle build.gradle.kts composer.json mix.exs CMakeLists.txt Makefile 2>/dev/null; ls *.uproject *.csproj *.sln 2>/dev/null
File Landscape
!find . -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/vendor/*' -not -path '*/target/*' -not -path '*/__pycache__/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/.next/*' -type f | grep -oE '\.[a-zA-Z0-9]+$' | sort | uniq -c | sort -rn | head -20
Repository State
!git status --short 2>/dev/null | head -10; echo "---"; git log --oneline -3 2>/dev/null
Source File Count
!find . -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/vendor/*' -not -path '*/target/*' -not -path '*/__pycache__/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/.next/*' -type f \( -name '*.js' -o -name '*.jsx' -o -name '*.ts' -o -name '*.tsx' -o -name '*.py' -o -name '*.rs' -o -name '*.go' -o -name '*.rb' -o -name '*.java' -o -name '*.kt' -o -name '*.cs' -o -name '*.cpp' -o -name '*.h' -o -name '*.php' -o -name '*.ex' -o -name '*.exs' -o -name '*.md' -o -name '*.vue' -o -name '*.svelte' \) 2>/dev/null | wc -l
Mode Detection
Parse $ARGUMENTS to determine:
- Mode: If arguments contain
--fix,fix,clean,cleanup, orremove→ Fix Mode. Otherwise → Report Mode (read-only). - Scope: If arguments contain a directory path (e.g.,
src/,lib/) or file pattern (e.g.,*.ts), use that as the analysis scope. Otherwise, scan the full project. - Category filter: If arguments mention a specific category (e.g., "unused deps", "orphaned files", "commented code"), only run that category's analysis.
Pre-Analysis: Determine Project Type and Strategy
Based on the detected manifest files and file extensions above, determine:
- Project type(s): JS/TS, Python, Rust, Go, Unreal Engine, C#, Ruby, Java/Kotlin, PHP, Elixir, C/C++, Content/Docs, or Multi-language
- Source file extensions to analyze
- Import/require patterns for this language
- Export/public patterns for this language
- Comment syntax for this language
- Dependency manifest and how to parse it
- Entry points to exclude from orphan detection
- Test file patterns (e.g.,
*.test.ts,*_test.go,test_*.py) - Asset directories to scan (e.g.,
public/,static/,assets/,Content/) - Config files to check for staleness
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.
- 11d ago First seen · 307 lines · 23 tokens per session scan A 84d8cc933f49
dead-code is a command published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 3,140 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-08-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.