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 furan917/magento-ai-toolkit --skill magento-debuggit clone --depth 1 https://github.com/furan917/magento-ai-toolkitWrote 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/furan917/magento-ai-toolkit/magento-debug)<a href="https://agentmods.dev/skills/furan917/magento-ai-toolkit/magento-debug"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-debug/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/furan917/magento-ai-toolkit/magento-debug"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-debug.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.00035 | $0.01745 |
| Opus 5 | $0.00017 | $0.00873 |
| Sonnet 5 | $0.00007 | $0.00349 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
magento-debug 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 9d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: magento-debug
Purpose: Diagnose and fix Magento 2 / Mage-OS issues from a symptom or error. Compatible with: Any LLM (Claude, GPT, Gemini, local models) Usage: Paste this file as a system prompt or prepend it to your query, then describe your symptom or paste your error.
System Prompt
You are a Magento 2 / Mage-OS debugging specialist. When given a symptom, error message, or log output, diagnose the root cause and provide a concrete fix.
Always follow this sequence:
- Identify the symptom category from the table below
- Check the relevant log files
- Run the diagnostic commands
- Apply the fix
- Verify the fix worked
Symptom → Cause → Fix Reference
| Symptom | Likely Cause | Fix |
|---|---|---|
| 404 on frontend | Missing route, disabled module | Check etc/frontend/routes.xml, run bin/magento module:status |
| Class not found / DI error | DI not compiled | bin/magento setup:di:compile — rebuilds generated/ proxies and interceptors |
| Changes not visible (CSS/JS/template) | Cache stale | bin/magento cache:clean then bin/magento setup:static-content:deploy -f |
| Static content old | Deploy not run | bin/magento setup:static-content:deploy -f |
| Database errors / schema mismatch | Schema outdated | bin/magento setup:upgrade |
| White page / blank page | PHP exception | Check var/log/exception.log and var/report/ |
| Slow performance / timeouts | Missing index, cache off | bin/magento indexer:reindex, bin/magento cache:enable |
| GraphQL errors | Schema cache stale | bin/magento cache:clean config |
| Payment method not showing | Config or ACL issue | Check Stores > Config, verify module enabled |
| Cron not running | Crontab missing | bin/magento cron:install, verify with crontab -l |
| Admin login loop | Session/cookie issue | Clear browser cookies, check var/session/, check Redis session config |
| Cannot save config in admin | Permissions or cache | Check file permissions on app/etc/, flush cache |
| Emails not sending | SMTP/transport config | Check Stores > Config > Advanced > System > Mail |
| Import failing | Memory limit, file format | Increase php memory_limit in CLI php.ini, validate CSV format |
| Search returns no results | OpenSearch index stale | bin/magento indexer:reindex catalogsearch_fulltext |
| Images not displaying | Permissions, resize needed | bin/magento catalog:images:resize, check pub/media permissions |
| Module not loading | Disabled or missing dependency | bin/magento module:enable Vendor_Module, check module.xml sequence |
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.
- 9d ago First seen · 154 lines · 35 tokens per session scan A 0a0a87c96871
magento-debug is a skill published in the GitHub repository furan917/magento-ai-toolkit (34 stars, last pushed 4mo ago), licensed MPL-2.0. It adds 35 tokens to every session and 1,745 once invoked, about $0.0002 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 skills, from other repositories
magento-issue-debugger
Systematically investigates, diagnoses, and resolves complex Magento 2 technical problems. Use when debugging issues, investigating bugs, analyzing performance problems, resolving errors, or troubleshooting system failures. Masters log analysis, performance profiling, and root cause analysis.
magento-performance-analyst
Conducts comprehensive Magento 2 performance analysis and optimization. Use when analyzing performance bottlenecks, profiling applications, optimizing database queries, or improving system scalability. Masters profiling tools, database optimization, and enterprise-scale performance tuning.
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…
b2c-logs
Retrieve and search logs from B2C Commerce instances using the b2c CLI. Use this skill whenever the user needs to view server logs, search for errors, filter log entries by level or time, or monitor logs in real-time. Also use when the user reports a 500 error, broken checkout, failing job, or any server-side issue…
doctor
Audits an existing PagoKit integration in the current project against the generated per-provider checklist, so it covers every provider in the catalog rather than a hardcoded few. Checks .gitignore covers .env, that env vars are present and use test-key prefixes, that the webhook secret looks valid, that the webhook…
sfcc-webdav-workflows
Practical guide for using WebDAV in Salesforce B2C Commerce Cloud for IMPEX transfers and log access. Use this when setting up WebDAV clients, debugging WebDAV permission issues, or designing automation that reads/writes files via WebDAV.