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 OrcaQubits/agentic-commerce-skills-plugins --skill magento-apigit clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-pluginsWrote 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/orcaqubits/agentic-commerce-skills-plugins/magento-api)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/magento-api"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/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/orcaqubits/agentic-commerce-skills-plugins/magento-api"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/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.00049 | $0.00837 |
| Opus 5 | $0.00024 | $0.00418 |
| Sonnet 5 | $0.00010 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
magento-api 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 3d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 REST & GraphQL API Development
Before writing code
Fetch live docs:
- Fetch
https://developer.adobe.com/commerce/webapi/for Web API overview - Fetch
https://developer.adobe.com/commerce/webapi/graphql/develop/for GraphQL development guide - Fetch
https://developer.adobe.com/commerce/webapi/get-started/for authentication - Web-search
site:developer.adobe.com commerce php development components web-apifor webapi.xml reference
REST API
How It Works
REST endpoints map HTTP methods + URL paths to service contract methods. Defined in etc/webapi.xml.
webapi.xml Structure
Each route defines:
url— endpoint path (e.g.,/V1/custom/items/:id)method— HTTP method (GET, POST, PUT, DELETE)service— class + method implementing the endpointresource— ACL resource for authorization
Path parameters (:id) map to method parameters by name.
Authentication Types
| Type | Header | Use Case |
|---|---|---|
| Admin Token | Authorization: Bearer <token> |
Back-office integrations |
| Customer Token | Authorization: Bearer <token> |
Customer-facing apps |
| OAuth 1.0a | OAuth headers | Third-party integrations |
| Session | PHP session cookie | Storefront JS widgets |
| Anonymous | resource="anonymous" |
Public endpoints |
Swagger/OpenAPI
Available at /rest/<store>/schema — auto-generated from webapi.xml and service contracts.
GraphQL API
How It Works
GraphQL uses a single endpoint (/graphql) with schema files and resolver classes.
Schema Files (schema.graphqls)
Define types, queries, and mutations in etc/schema.graphqls:
- Custom types with fields
- Query definitions mapping to resolver classes
- Mutation definitions with input/output types
- Extend existing types with new fields
Resolver Classes
Implement Magento\Framework\GraphQl\Query\ResolverInterface:
resolve(Field $field, $context, ResolveInfo $info, array $value = null, array $args = null)- Return arrays matching the GraphQL type definition
- Context provides store, customer, and extension attributes
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.
- 3d ago First seen · 97 lines · 49 tokens per session scan A 0eca55bdb5f8
magento-api is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 837 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-09-15.
Other skills, from other repositories
archestra-dev-interactions-migrations
Use BEFORE writing or running any Drizzle migration that touches the interactions table (or any other very large, write-hot table). The interactions table is the platform's biggest, append-heavy table — every LLM proxy call writes a row — so a careless migration can take a write-blocking lock and stall the proxy.…
archestra-dev-llm-providers
Use when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching provider credentials/enums and model constants.
archestra-dev-backend
Use when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
debridge
Complete deBridge Protocol SDK for building cross-chain bridges, message passing, and token transfers on Solana. Use when building cross-chain applications, bridging assets between Solana and EVM chains, or implementing trustless external calls.
mppx
TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.
near-intents
Cross-chain token swap integration using NEAR Intents 1Click API. Use when building swap widgets, bridge interfaces, or multi-chain transfers across EVM, Solana, NEAR, TON, Stellar, and Tron.