Analysis updated 2026-05-18
Audit a CLAUDE.md file to find configurations that quietly add token cost to every single interaction.
Check before adding a new Claude plugin whether its functionality already exists in another installed skill.
Find activation cascades in a Claude Code setup where one skill repeatedly triggers others and multiplies processing cost.
| kyontanaka/yagni-auditor | 195516184-a11y/esp32-mcp-parenting-robot | a-bissell/unleash-lite | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | — | — | Python |
| Setup difficulty | easy | moderate | hard |
| Complexity | 1/5 | 3/5 | 4/5 |
| Audience | developer | general | researcher |
Figures from each repo's GitHub metadata at analysis time.
Copy yagni-audit.md to ~/.claude/skills/, no dependencies or package installation required.
YAGNI stands for "You Aren't Gonna Need It," a software design principle warning against adding things before they are actually required. YAGNI Auditor applies that idea to Claude Code skills, plugins, and configuration files. You give it a CLAUDE.md file, a list of installed skills, or a configuration to review, and it analyzes the setup to find things that add cost or confusion without adding genuine value. The audit runs through four phases. The first looks for files and configurations that load on every interaction whether or not they are relevant, adding token usage quietly in the background. The second distinguishes between instructions that actually change how Claude behaves versus lists and catalogs that are just directories of information with no effect on behavior. The third checks whether multiple installed skills compete to handle the same request, which forces the AI to spend time deciding between them rather than doing the task. The fourth phase, added in version 2.0, detects activation cascades: situations where one skill triggers another which triggers a third, multiplying the processing involved for a single user request. The output is a scored report, zero to ten per architecture reviewed, sorted into critical issues, moderate issues, and things that look fine, with a post-audit checklist of concrete actions to take. The tool is a Claude Code skill, meaning it is a markdown file you copy into the Claude skills directory. Installation is a single command. There are no dependencies and the audit never runs external code, makes outbound network connections for data collection, or sends telemetry anywhere. Everything stays local. The README notes what this tool does not cover: it does not detect malware, does not analyze application source code, and does not do dynamic analysis that would require executing any code being reviewed. The project is licensed under MIT.
A Claude Code skill that runs static analysis on your skills, plugins, and CLAUDE.md files to find unnecessary complexity, silent token costs, duplicate skills, and activation cascades, producing a scored 0-10 audit report.
Use, modify, and distribute freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.