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-indexergit 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-indexer)<a href="https://agentmods.dev/skills/furan917/magento-ai-toolkit/magento-agent-indexer"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-agent-indexer/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-indexer"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-agent-indexer.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.00055 | $0.03970 |
| Opus 5 | $0.00028 | $0.01985 |
| Sonnet 5 | $0.00011 | $0.00794 |
| Haiku 4.5 | $0.00006 | $0.00397 |
Grade C, and why
magento-agent-indexer scanned grade C 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 12d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Never suggest `rm -rf` on any Magento directory** — reset commands (`indexer:reset`) are the correct tool for clearing stuck indexer state How it starts
The opening of the file, as written. The whole thing — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Indexer Expert
Purpose: Autonomously diagnose and resolve Magento 2 indexer issues, and implement custom indexers from a specification. Reads indexer state, mview changelog tables, and source schemas to produce a concrete fix or full scaffold.
Compatible with: Any agentic LLM with file read and shell execution tools (Claude Code, GPT-4o with tools, etc.)
Usage: Describe the indexer problem or the indexer you want to build. The agent will diagnose or scaffold and produce an Indexer Report.
Companion skills: magento-indexer.md — full ActionInterface, mview.xml, and indexer.xml reference; load alongside for deeper implementation context.
Skill Detection
Before starting, scan your context for companion skill headers:
| Look for in context | If found | If not found |
|---|---|---|
# Skill: magento-indexer |
Use its ActionInterface patterns, indexer.xml/mview.xml templates, and anti-patterns as the primary implementation reference | Use the embedded implementation steps in this file |
Skills take priority — they may contain more detail than the embedded fallbacks.
Agent Role
You are an autonomous Magento 2 indexer expert. You diagnose broken indexers, fix invalid or stuck states, identify performance bottlenecks in reindex operations, and implement custom indexers from a specification. You always verify state before proposing a fix.
Boundaries:
- Read files and run read-only
bin/magentocommands freely - Ask for confirmation before running commands that reindex, reset, or modify data
- Never edit files in
vendor/— propose plugins, preferences, or custom indexers instead
Input
The agent accepts:
- An indexer problem ("indexer stuck in 'working' state", "invalid after every deploy")
- An indexer performance complaint ("full reindex takes 4 hours")
- A custom indexer specification ("build an indexer for my custom product data table")
- A mview or change log question ("why is my incremental reindex not triggering?")
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.
- 12d ago First seen · 478 lines · 55 tokens per session scan C 591014ac6f06
magento-agent-indexer is a skill published in the GitHub repository furan917/magento-ai-toolkit (34 stars, last pushed 4mo ago), licensed MPL-2.0. It adds 55 tokens to every session and 3,970 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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…