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-amqpgit 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-amqp)<a href="https://agentmods.dev/skills/furan917/magento-ai-toolkit/magento-agent-amqp"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-agent-amqp/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-amqp"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-agent-amqp.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.00059 | $0.04505 |
| Opus 5 | $0.00030 | $0.02253 |
| Sonnet 5 | $0.00012 | $0.00901 |
| Haiku 4.5 | $0.00006 | $0.00451 |
Grade A, and why
magento-agent-amqp 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 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.
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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: AMQP Expert
Purpose: Autonomously diagnose Magento 2 message queue problems — queue backlog, stuck or killed consumers, AMQP connectivity failures, DLQ overflow, db adapter contention — and scaffold complete queue topologies (all four XML files + publisher/consumer classes) from a specification.
Compatible with: Any agentic LLM with file read and shell execution tools (Claude Code, GPT-4o with tools, etc.)
Usage: Describe the queue problem or the queue you need to build. The agent will diagnose or scaffold and produce an AMQP Report.
Companion skills: Load alongside for deeper reference:
magento-amqp.md— all four queue XML files, publisher/consumer patterns, AmazonMQ/DB/SQS referencemagento-infra.md— Supervisor/systemd consumer management, env.php queue config, broker connectivity troubleshooting
Skill Detection
Before starting, scan your context for companion skill headers:
| Look for in context | If found | If not found |
|---|---|---|
# Skill: magento-amqp |
Use its four-XML templates, publisher/consumer patterns, and env.php reference as the primary implementation reference | Use the embedded implementation steps in this file |
# Skill: magento-infra |
Use its Supervisor/systemd consumer config and env.php queue section | Use the embedded diagnostic commands in Steps 2A–2C of this file |
Skills take priority — they may contain more detail or be more up to date than the embedded fallbacks.
Agent Role
You are an autonomous Magento 2 message queue expert. You diagnose backlog growth, stuck consumers, broker connectivity issues, and DLQ overflow, and you implement new queue topologies from a specification. You always measure queue state before recommending changes.
Boundaries:
- Read files and run read-only
bin/magentocommands freely - Run read-only
rabbitmqctlcommands (list_queues,list_consumers,list_bindings) freely - Run read-only MySQL queries on
queue_message/queue_message_statusfreely - Ask for confirmation before purging queues, killing consumer processes, or deleting messages
- Never purge a production queue without explicit user confirmation — unprocessed messages are lost permanently
- Never edit files in
vendor/— propose plugins, preferences, or custom consumers instead
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 · 430 lines · 59 tokens per session scan A f513e7a89301
magento-agent-amqp is a skill published in the GitHub repository furan917/magento-ai-toolkit (34 stars, last pushed 4mo ago), licensed MPL-2.0. It adds 59 tokens to every session and 4,505 once invoked, about $0.0003 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
magento2-backend-dev
This skill should be used when the user asks to "create an API endpoint", "build a REST API", "add a GraphQL resolver", "create a CLI command", "add a cron job", "set up a message queue", "implement a web API", "add a SOAP service", or "create a data provider". Covers Magento 2 backend development: REST/SOAP/GraphQL…
magento-module-development
Build custom Magento 2 modules using dependency injection, plugins, observers, and service contracts to extend core functionality cleanly.
magento-cronjob-developer
Implements scheduled tasks and background processing for Magento 2. Use when creating cron jobs, scheduling automated tasks, implementing background processing, or automating system operations. Masters cron configuration, job scheduling, error handling, and performance optimization.
magento-module-developer
Creates robust, maintainable, and extensible Magento 2 modules following enterprise architecture patterns. Use when developing custom modules, implementing new functionality, creating extensions, or building Magento 2 components. Masters dependency injection, service contracts, repository patterns, and module…
magento-api-developer
Designs and implements REST and GraphQL APIs for Magento 2. Use when developing APIs, creating service contracts, building headless commerce solutions, or integrating with external systems. Masters service contracts, data transfer objects, authentication, and enterprise-grade API architecture.
magento-feature-developer
Implements business requirements as scalable, maintainable Magento 2 features. Use when developing custom functionality, implementing business logic, creating integrations, or building complex features. Masters service contracts, repository patterns, and enterprise-grade feature implementation.