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/CrashBytes/claude-role-skillsWrote 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/crashbytes/claude-role-skills/legacy-audit)<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/legacy-audit"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/legacy-audit/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/crashbytes/claude-role-skills/legacy-audit"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/legacy-audit.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.00007 | $0.00392 |
| Opus 5.5 | $0.00003 | $0.00157 |
| Sonnet 5.5 | $0.00001 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
legacy-audit 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.
What it actually says
Legacy System Audit
Audit a codebase to assess modernization readiness and identify migration priorities.
Arguments
Target to audit: $ARGUMENTS
Workflow
-
Inventory the system
- Scan the codebase structure and file types
- Identify languages, frameworks, and their versions
- Map dependency graph (direct and transitive)
- Detect deprecated APIs and end-of-life dependencies
-
Assess code health
- Estimate test coverage (presence and quality of test files)
- Check for documentation (README, API docs, inline comments)
- Identify code smells: god classes, long methods, circular dependencies
- Check for hardcoded configuration, magic numbers, dead code
-
Evaluate architecture
- Monolith vs modular vs microservices
- Coupling analysis: how tightly are components connected?
- Identify natural service boundaries (bounded contexts)
- Database structure: single DB, shared schemas, data ownership
-
Security assessment
- Outdated dependencies with known CVEs
- Authentication and authorization patterns
- Secret management practices
- Input validation and output encoding
-
Score modernization readiness Rate each dimension 1-5:
- Code quality and maintainability
- Test coverage and confidence
- Documentation completeness
- Architecture modularity
- Dependency health
- Security posture
- Team knowledge and skills
-
Output
- System inventory summary
- Health scorecard (radar chart dimensions)
- Top 10 modernization priorities ranked by impact and effort
- Recommended migration approach (based on scores)
- Quick wins that can be done before a full migration
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 · 57 lines · 7 tokens per session scan A ebf0ce0831d8
legacy-audit is a command published in the GitHub repository CrashBytes/claude-role-skills (8 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 392 once invoked, about $0.0000 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-31.
legacy-audit compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| legacy-auditCrashBytes/claude-role-skills | Command | 8 | 8mo ago | Apache-2.0 | A | 7 | Claude Code |
| review-prMadaraUchiha-314/the-loop | Command | 8 | 12d ago | MIT | A | 34 | Claude Code |
| reviewjjmartres/ai-coding-agents | Command | 48 | 20d ago | MIT | A | 3 | Claude Code |
| clean-checkTeamManagementPlugin/claude-plugin | Command | 6 | 28d ago | MIT | A | 27 | Claude Code |
| resolve-reviewsergeyklay/.agents | Command | 6 | 6d ago | Apache-2.0 | A | 15 | Claude Code |
| pr-descriptionAmey-Thakur/AI-SKILLS | Command | 14 | 2mo ago | MIT | A | 23 | Claude Code |
| refactor-codeAmey-Thakur/AI-SKILLS | Command | 14 | 2mo ago | MIT | A | 17 | Claude Code |