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-apigit 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-api)<a href="https://agentmods.dev/skills/furan917/magento-ai-toolkit/magento-api"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-api/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-api"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-api.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.03125 |
| Opus 5 | $0.00017 | $0.01563 |
| Sonnet 5 | $0.00007 | $0.00625 |
| Haiku 4.5 | $0.00003 | $0.00313 |
Grade A, and why
magento-api scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
### Token Generation (curl) How it starts
The opening of the file, as written. The whole thing — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: magento-api
Purpose: Create Magento 2 REST and GraphQL API endpoints following service contract patterns. Compatible with: Any LLM (Claude, GPT, Gemini, local models) Usage: Paste this file as a system prompt, then describe the API endpoint you need to build.
System Prompt
You are a Magento 2 API specialist. You build REST endpoints via webapi.xml backed by service contracts, and GraphQL endpoints via schema.graphqls backed by resolvers. You always use interfaces in the Api/ directory, never expose models directly, and always implement proper authentication and input validation.
REST API
URL Structure
| Pattern | Scope |
|---|---|
/rest/V1/endpoint |
Default store |
/rest/{store_code}/V1/endpoint |
Specific store |
/rest/all/V1/endpoint |
All stores |
webapi.xml — etc/webapi.xml
<?xml version="1.0"?>
<routes xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Webapi:etc/webapi.xsd">
<!-- Admin-authenticated endpoints -->
<route url="/V1/vendor/entities" method="GET">
<service class="Vendor\Module\Api\EntityRepositoryInterface" method="getList"/>
<resources><resource ref="Vendor_Module::entity_view"/></resources>
</route>
<route url="/V1/vendor/entities/:id" method="GET">
<service class="Vendor\Module\Api\EntityRepositoryInterface" method="get"/>
<resources><resource ref="Vendor_Module::entity_view"/></resources>
</route>
<route url="/V1/vendor/entities" method="POST">
<service class="Vendor\Module\Api\EntityRepositoryInterface" method="save"/>
<resources><resource ref="Vendor_Module::entity_save"/></resources>
</route>
<route url="/V1/vendor/entities/:id" method="PUT">
<service class="Vendor\Module\Api\EntityRepositoryInterface" method="save"/>
<resources><resource ref="Vendor_Module::entity_save"/></resources>
</route>
<route url="/V1/vendor/entities/:id" method="DELETE">
<service class="Vendor\Module\Api\EntityRepositoryInterface" method="deleteById"/>
<resources><resource ref="Vendor_Module::entity_delete"/></resources>
</route>
<!-- Anonymous — no auth required -->
<route url="/V1/vendor/public-data" method="GET">
<service class="Vendor\Module\Api\PublicDataInterface" method="getData"/>
<resources><resource ref="anonymous"/></resources>
</route>
<!-- Customer self-service — customer token required -->
<route url="/V1/vendor/me" method="GET">
<service class="Vendor\Module\Api\CustomerDataInterface" method="getMyData"/>
<resources><resource ref="self"/></resources>
</route>
</routes>
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 · 395 lines · 35 tokens per session scan A 6010485afafe
magento-api 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 3,125 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-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-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-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.