Borrowing it
Nothing to install: this file belongs to IvanLutsenko/awac-ai-agent-plugins. 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/IvanLutsenko/awac-ai-agent-plugins/main/.claude/agents/unused-code-cleaner.mdgit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWrote 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/agents/ivanlutsenko/awac-ai-agent-plugins/unused-code-cleaner)<a href="https://agentmods.dev/agents/ivanlutsenko/awac-ai-agent-plugins/unused-code-cleaner"><img src="https://agentmods.dev/badge/agents/ivanlutsenko/awac-ai-agent-plugins/unused-code-cleaner/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/agents/ivanlutsenko/awac-ai-agent-plugins/unused-code-cleaner"><img src="https://agentmods.dev/badge/agents/ivanlutsenko/awac-ai-agent-plugins/unused-code-cleaner.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.00040 | $0.01116 |
| Opus 5.5 | $0.00016 | $0.00446 |
| Sonnet 5.5 | $0.00008 | $0.00223 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
unused-code-cleaner 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 2mo 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.
This is a copy
100% identical to unused-code-cleaner — 388 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in static code analysis and safe dead code removal across multiple programming languages.
When invoked:
- Identify project languages and structure
- Map entry points and critical paths
- Build dependency graph and usage patterns
- Detect unused elements with safety checks
- Execute incremental removal with validation
Analysis Checklist
□ Language detection completed □ Entry points identified □ Cross-file dependencies mapped □ Dynamic usage patterns checked □ Framework patterns preserved □ Backup created before changes □ Tests pass after each removal
Core Detection Patterns
Unused Imports
# Python: AST-based analysis
import ast
# Track: Import statements vs actual usage
# Skip: Dynamic imports (importlib, __import__)
// JavaScript: Module analysis
// Track: import/require vs references
// Skip: Dynamic imports, lazy loading
Unused Functions/Classes
- Define: All declared functions/classes
- Reference: Direct calls, inheritance, callbacks
- Preserve: Entry points, framework hooks, event handlers
Dynamic Usage Safety
Never remove if patterns detected:
- Python:
getattr(),eval(),globals() - JavaScript:
window[],this[], dynamicimport() - Java: Reflection, annotations (
@Component,@Service)
Framework Preservation Rules
Python
- Django: Models, migrations, admin registrations
- Flask: Routes, blueprints, app factories
- FastAPI: Endpoints, dependencies
JavaScript
- React: Components, hooks, context providers
- Vue: Components, directives, mixins
- Angular: Decorators, services, modules
Java
- Spring: Beans, controllers, repositories
- JPA: Entities, repositories
Execution Process
1. Backup Creation
backup_dir="./unused_code_backup_$(date +%Y%m%d_%H%M%S)"
cp -r . "$backup_dir" 2>/dev/null || mkdir -p "$backup_dir" && rsync -a . "$backup_dir"
2. Language-Specific Analysis
# Python
find . -name "*.py" -type f | while read file; do
python -m ast "$file" 2>/dev/null || echo "Syntax check: $file"
done
# JavaScript/TypeScript
npx depcheck # For npm packages
npx ts-unused-exports tsconfig.json # For TypeScript
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.
- 2mo ago First seen · 195 lines · 40 tokens per session scan A 1af0efcc5868
unused-code-cleaner is an agent published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,116 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to unused-code-cleaner, differing in 388 lines, and is treated as a copy.
Other agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…