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.
npx skills add maxnorm/magento2-agent-skills --skill magento-issue-debuggergit clone --depth 1 https://github.com/maxnorm/magento2-agent-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/skills/maxnorm/magento2-agent-skills/magento-issue-debugger)<a href="https://agentmods.dev/skills/maxnorm/magento2-agent-skills/magento-issue-debugger"><img src="https://agentmods.dev/badge/skills/maxnorm/magento2-agent-skills/magento-issue-debugger/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/skills/maxnorm/magento2-agent-skills/magento-issue-debugger"><img src="https://agentmods.dev/badge/skills/maxnorm/magento2-agent-skills/magento-issue-debugger.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.00054 | $0.01492 |
| Opus 5.5 | $0.00022 | $0.00597 |
| Sonnet 5.5 | $0.00011 | $0.00298 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
magento-issue-debugger 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 1mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 Issue Debugger
Expert specialist in systematically investigating, diagnosing, and resolving complex technical problems across all layers of the Magento stack.
When to Use
- Debugging production issues
- Investigating bugs and errors
- Analyzing performance problems
- Resolving system failures
- Troubleshooting integration issues
- Diagnosing cache or indexing problems
Debugging Methodologies
Systematic Investigation
- Problem Assessment: Establish consistent steps to reproduce the problem
- Environment Documentation: Catalog system configuration and environment details
- Impact Analysis: Determine scope, frequency, and business impact
- Timeline Analysis: Establish when the issue started and what changed
- Isolation Testing: Disable modules and features to isolate the issue
Root Cause Analysis
- Hypothesis Testing: Form and test theories methodically
- Data Collection: Gather logs, configuration, and performance metrics
- Code Analysis: Review recent code changes and related modules
- Database Investigation: Check for data corruption or migration issues
- Deep Dive: Dig deep to find underlying causes rather than treating symptoms
Issue Investigation Process
1. Problem Assessment
- Issue Reproduction: Establish consistent steps to reproduce
- Environment Documentation: Catalog system configuration
- Impact Analysis: Determine scope and business impact
- Timeline Analysis: Establish when issue started
- User Impact: Understand how issue affects different user types
2. Data Collection
- Log Gathering: Collect relevant logs from all system components
- Magento logs:
var/log/ - PHP error logs
- Web server logs (Apache/Nginx)
- Database slow query logs
- Magento logs:
- Configuration Review: Examine module configurations and system settings
- Code Analysis: Review recent code changes and related modules
- Database Investigation: Check for data corruption or migration issues
- Performance Metrics: Gather timing and resource usage data
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.
- 1mo ago First seen · 170 lines · 54 tokens per session scan A d198bae09c3f
magento-issue-debugger is a skill published in the GitHub repository maxnorm/magento2-agent-skills (31 stars, last pushed 9mo ago), licensed MIT. It adds 54 tokens to every session and 1,492 once invoked, about $0.0002 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-30.
Other skills, from other repositories
magento-agent-search
Autonomously diagnose Magento 2 catalog search problems — missing products, 0 results, wrong relevance, stuck reindex, cluster red/yellow, disk-watermark read-only — and advise on ES 7 → ES 8 or ES 7 → OpenSearch migrations. Produces a Search Report with engine, version, cluster health, root cause, fix, and…
magento-agent-bug-triage
Autonomously diagnose Magento 2 bugs from a symptom or error — reads logs, checks system state, identifies root cause, and produces a concrete fix plan.
magento-debug
Diagnose and fix Magento 2 issues from a symptom or error. Use when debugging white pages, 500 errors, performance issues, or unexpected behaviour.
magento-agent-indexer
Autonomously diagnose Magento 2 indexer issues, fix invalid or stuck indexers, and scaffold custom indexers from a spec — reads indexer state, mview changelog, and DB schema to produce a concrete fix or implementation plan.
revenuecat-troubleshoot
Diagnose and resolve RevenueCat integration issues — inspects dashboard configuration through the RevenueCat MCP, walks the SDK debug logs, and covers code-side gotchas. Use when the user says offerings are empty, products not loading, entitlement not active after purchase, paywall won't load, transactions not…
magento-module-development
Build custom Magento 2 modules using dependency injection, plugins, observers, and service contracts to extend core functionality cleanly.