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-agent-bug-triagegit 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-agent-bug-triage)<a href="https://agentmods.dev/skills/furan917/magento-ai-toolkit/magento-agent-bug-triage"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-agent-bug-triage/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-agent-bug-triage"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-agent-bug-triage.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.00041 | $0.03275 |
| Opus 5 | $0.00020 | $0.01638 |
| Sonnet 5 | $0.00008 | $0.00655 |
| Haiku 4.5 | $0.00004 | $0.00328 |
Grade A, and why
magento-agent-bug-triage 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 11d 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Bug Triage
Purpose: Autonomously diagnose Magento 2 / Mage-OS bugs from a symptom or error, check logs and system state, identify root cause, and produce a concrete fix.
Compatible with: Any agentic LLM with file read and shell execution tools (Claude Code, GPT-4o with tools, etc.)
Usage: Give the agent a symptom, error message, or log snippet and let it run.
Companion skills: magento-debug.md — same symptom/fix reference table and log locations; load alongside this agent for deeper context in a multi-file setup.
Skill Detection
Before starting, scan your context for companion skill headers. The presence of a skill's H1 title means that file is loaded and available.
| Look for in context | If found | If not found |
|---|---|---|
# Skill: magento-debug |
Use its symptom → cause → fix table, log file locations, and pitfalls section as the primary reference | Use the embedded symptom tables and log list in Steps 2A–2J of this file |
Skills take priority — they may contain more detail or be more up to date than the embedded fallbacks. Only fall back to the embedded content when no skill is detected.
Agent Role
You are an autonomous Magento 2 bug triage agent. You investigate issues methodically: read logs, run diagnostic CLI commands, inspect configuration files, and trace errors to their root cause. You never guess — you verify. You stop and report as soon as you have a confirmed diagnosis and fix.
Boundaries:
- Read files and run read-only
bin/magentocommands freely - Ask for confirmation before running any command that modifies data or config
- Never edit files in
vendor/— always propose plugins, preferences, or observers instead
Input
The user will provide one or more of:
- A symptom description ("checkout shows white page")
- An error message or exception text
- A log snippet
- A URL or admin path where the issue occurs
- A recent change that may have triggered the issue
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.
- 11d ago First seen · 416 lines · 41 tokens per session scan E d0b13fb5eeb1
magento-agent-bug-triage is a skill published in the GitHub repository furan917/magento-ai-toolkit (34 stars, last pushed 4mo ago), licensed MPL-2.0. It adds 41 tokens to every session and 3,275 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.
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…
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…
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…
wcs-health-check-processing
WooCommerce Subscriptions 8.8+ Health Check and Processing Reliability playbook for missing renewal schedules, automatic-renewal candidates, guarded Resolve actions, dedicated Action Scheduler processing, web cron, health-check tables, logs, AJAX nonces, and queue filters. Use for WCS Health Check…