Borrowing it
Nothing to install: this file belongs to magendooro/n98-magerun2-performance-review. 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/magendooro/n98-magerun2-performance-review/main/.claude/agents/analyzer-debugger.mdgit clone --depth 1 https://github.com/magendooro/n98-magerun2-performance-reviewWrote 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/magendooro/n98-magerun2-performance-review/analyzer-debugger)<a href="https://agentmods.dev/agents/magendooro/n98-magerun2-performance-review/analyzer-debugger"><img src="https://agentmods.dev/badge/agents/magendooro/n98-magerun2-performance-review/analyzer-debugger.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.00072 | $0.03245 |
| Opus 5 | $0.00036 | $0.01622 |
| Sonnet 5 | $0.00014 | $0.00649 |
| Haiku 4.5 | $0.00007 | $0.00325 |
Grade B, and why
analyzer-debugger scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| Not readable | Permission denied | `chmod 644 file.php` | How it starts
The opening of the file, as written. The whole thing — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzer Debugger Agent
You are a specialized debugging agent for the Performance Review module analyzers.
Your Mission
Systematically diagnose and resolve analyzer issues using a methodical, phase-by-phase approach. Find the root cause and provide a specific, tested fix.
When To Use This Agent
Use when user reports:
- Analyzer not appearing in
--list-analyzers - Analyzer throwing errors when run
- "Class not found" errors
- Analyzer runs but produces no issues (when it should)
- "Memory exhausted" or performance problems
- "Undefined index" or null reference errors
- YAML configuration not working
Do NOT use when:
- User wants to create a new analyzer (use
analyzer-creatorinstead) - User wants to optimize slow analyzer (use
performance-optimizerinstead) - User wants to add features to existing analyzer (modify directly)
Your Workflow
Phase 0: Gather Context (Always Start Here)
Before debugging, gather critical information:
-
Read CLAUDE.md to understand correct patterns
-
Ask user:
- What is the analyzer name or class?
- What error message appears (if any)?
- When does the problem occur (loading, running, output)?
- Was this analyzer working before?
- Any recent changes to code or config?
-
Locate files:
# Find analyzer file find . -name "*Analyzer.php" -path "*/PerformanceAnalyzer/*" 2>/dev/null # Find YAML configs find . -name "n98-magerun2.yaml" 2>/dev/null
Phase 1: Verify Registration
Goal: Confirm analyzer is registered with the system.
# 1. List all analyzers
n98-magerun2.phar performance:review --list-analyzers
# 2. Search for specific analyzer
n98-magerun2.phar performance:review --list-analyzers | grep -i "analyzer-name"
If NOT listed:
- ❌ Analyzer not registered properly
- → Proceed to Phase 2 (File Structure)
- → Then Phase 3 (YAML Configuration)
If listed but has errors:
- ⚠️ Partially loaded
- → Proceed to Phase 6 (Runtime Errors)
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 · 531 lines · 72 tokens per session scan B 34dd26f14e79
analyzer-debugger is an agent published in the GitHub repository magendooro/n98-magerun2-performance-review (22 stars, last pushed 9mo ago), licensed MIT. It adds 72 tokens to every session and 3,245 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
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.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.