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 maxnorm/magento2-agent-skills --skill magento-feature-developergit clone --depth 1 https://github.com/maxnorm/magento2-agent-skillsWrote 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/maxnorm/magento2-agent-skills/magento-feature-developer)<a href="https://agentmods.dev/skills/maxnorm/magento2-agent-skills/magento-feature-developer"><img src="https://agentmods.dev/badge/skills/maxnorm/magento2-agent-skills/magento-feature-developer.svg" alt="Measured on agentmods" 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.00051 | $0.01217 |
| Opus 5 | $0.00026 | $0.00609 |
| Sonnet 5 | $0.00010 | $0.00243 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
magento-feature-developer 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 8d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 Feature Developer
Expert specialist in translating business requirements into robust, scalable technical solutions within the Magento ecosystem following Adobe Commerce best practices.
When to Use
- Implementing new business features
- Developing custom functionality
- Creating integrations with third-party systems
- Building complex business logic
- Extending existing Magento functionality
Feature Development Process
1. Discovery & Planning
- Requirements Analysis: Break down business requirements into technical specifications
- Stakeholder Interviews: Gather comprehensive requirements from business users
- Technical Analysis: Assess existing system capabilities and constraints
- Impact Assessment: Evaluate effects on performance, security, and scalability
- Resource Planning: Estimate development timeline and requirements
2. Architecture Design
- System Design: Create high-level architecture diagrams and component relationships
- Database Design: Plan entity relationships, indexes, and data migration strategies
- API Design: Define service contracts and data transfer objects
- Integration Points: Identify touchpoints with existing modules and third-party systems
- Performance Planning: Design for scalability and optimal response times
3. Implementation Strategy
- Module Structure: Organize code following Magento's module conventions
- Service Contracts: Implement clean API interfaces for feature contracts
- Repository Pattern: Build data access layers using Magento's repository pattern
- Configuration Management: Implement admin configuration options where appropriate
- Error Handling: Build robust error handling and logging mechanisms
4. Quality Assurance
- Unit Testing: Write comprehensive PHPUnit tests for business logic
- Integration Testing: Test feature integration with core Magento functionality
- Performance Testing: Ensure features don't degrade system performance
- Security Review: Validate security compliance and data protection
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.
- 8d ago First seen · 140 lines · 51 tokens per session scan A d58b05a1f48c
magento-feature-developer is a skill published in the GitHub repository maxnorm/magento2-agent-skills (29 stars, last pushed 7mo ago), licensed MIT. It adds 51 tokens to every session and 1,217 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-agent-amqp
Autonomously diagnose Magento 2 message queue problems — backlog growth, stuck consumers, broker connectivity, DLQ overflow — and scaffold new queues (communication, topology, consumer, publisher) from a specification. Produces an AMQP Report with root cause and fix.
magento-agent-api-builder
Autonomously generate a complete Magento 2 REST or GraphQL API from a plain-language spec — service contracts, repository, webapi.xml, and GraphQL schema with resolvers.
magento-agent-module-generator
Autonomously generate a complete, production-ready Magento 2 module from a plain-language spec — all files, directory structure, service contracts, and database schema.
magento-amqp
Configure Magento 2 message queues with AMQP (RabbitMQ, AmazonMQ), DB adapter, and all four required XML files. Use when building async processing, bulk operations, or decoupled architectures.
magento-api
Create Magento 2 REST and GraphQL API endpoints following service contract patterns. Use when building APIs, webapi.xml routes, or GraphQL resolvers.