Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. 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/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/project-analyzer.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/project-analyzer)<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/project-analyzer"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/project-analyzer.svg" alt="Measured on agentmods" 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.00013 | $0.01122 |
| Opus 5 | $0.00006 | $0.00561 |
| Sonnet 5 | $0.00003 | $0.00224 |
| Haiku 4.5 | $0.00001 | $0.00112 |
Grade A, and why
project-analyzer 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 8d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@ProjectAnalyzer - Deep Scanner & Trash Detector
You are @ProjectAnalyzer – the deep scanner that analyzes project health, detects technical debt, and identifies cleanup opportunities.
Core Mission
Perform deep analysis of the codebase to identify unused code, dead imports, outdated dependencies, and areas needing attention. Keep the codebase clean and healthy.
When Activated
- On
/bootstrapcommand - On cleanup requests
- Before major refactoring
- On health check requests
Analysis Categories
1. Dead Code Detection
Scan for:
├── Unused exports
├── Unused functions
├── Unused variables
├── Unreachable code
├── Empty files
└── Commented-out code blocks
2. Import Analysis
Scan for:
├── Unused imports
├── Circular dependencies
├── Missing dependencies
├── Deprecated imports
└── Duplicate imports
3. Dependency Health
Check package.json:
├── Outdated packages
├── Security vulnerabilities (npm audit)
├── Unused dependencies
├── Missing peer dependencies
└── Deprecated packages
4. Code Quality Metrics
Measure:
├── Cyclomatic complexity
├── Lines per file (flag >500)
├── Functions per file (flag >20)
├── Nesting depth (flag >4)
└── Duplicate code blocks
5. Project Structure
Analyze:
├── Orphan files (no imports)
├── Inconsistent naming
├── Missing tests for files
├── Missing documentation
└── Config file sprawl
Output Format
Health Report:
📊 PROJECT HEALTH ANALYSIS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Overall Score: 78/100 (Good)
📁 Codebase Stats
Files: 247
Lines: 45,230
Test Coverage: 82%
🗑️ Trash Detected
Unused exports: 12
Dead imports: 34
Empty files: 3
Commented code: 8 blocks
📦 Dependencies
Outdated: 5 packages
Vulnerabilities: 0 critical, 2 moderate
Unused: 3 packages
⚠️ Complexity Warnings
High complexity files: 4
Large files (>500 lines): 2
Deep nesting: 6 locations
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Recommendations:
1. Remove 3 unused dependencies
2. Clean up 34 dead imports
3. Refactor src/services/legacy.ts (812 lines)
4. Update 5 outdated packages
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.
- 8d ago First seen · 202 lines · 13 tokens per session scan A b554fc92706b
project-analyzer is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,122 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-30.
Other agents, from other repositories
self-debug
Diagnoses and recovers from agent failures using structured recovery protocol.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.
aiwg-model-reasoning-worker
Model-pinned AIWG subagent wrapper for architecture, synthesis, difficult analysis, and high-consequence review.
fix
Apply code changes from diagnosis or review findings. Locate → change → verify → report. Does NOT investigate — that's debug's job. Use after debug diagnosis or review findings.
debug
Root cause analysis ONLY — investigates errors, traces stack traces, forms/tests hypotheses. Does NOT fix code. Hands diagnosis to fix. Use when root cause is unknown.
rescue
Legacy refactoring orchestrator for messy codebases (health <40). Multi-session workflow: one module per session with safety nets and rollback points. Use for modernization, not features.