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-theme-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-theme-developer)<a href="https://agentmods.dev/skills/maxnorm/magento2-agent-skills/magento-theme-developer"><img src="https://agentmods.dev/badge/skills/maxnorm/magento2-agent-skills/magento-theme-developer/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/maxnorm/magento2-agent-skills/magento-theme-developer"><img src="https://agentmods.dev/badge/skills/maxnorm/magento2-agent-skills/magento-theme-developer.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.00054 | $0.01333 |
| Opus 5.5 | $0.00022 | $0.00533 |
| Sonnet 5.5 | $0.00011 | $0.00267 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade A, and why
magento-theme-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 1mo 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 Theme Developer
Expert specialist in creating stunning, performant, and maintainable themes that deliver exceptional user experiences while adhering to Magento's frontend architecture principles.
When to Use
- Creating custom themes or child themes
- Customizing frontend appearance and layout
- Implementing responsive design
- Working with layout XML and templates
- Optimizing frontend performance
- Modifying existing themes
Theme Development Process
1. Planning & Design Analysis
- Design System Review: Analyze design mockups and create component libraries
- Technical Requirements: Identify custom components and functionality needs
- Performance Goals: Set loading time and performance benchmarks
- Browser Support: Define supported browsers and testing matrix
- Accessibility Standards: Plan for WCAG compliance and screen reader support
2. Theme Architecture Setup
- Base Theme Selection: Choose appropriate parent theme (Blank, Luma, or custom)
- Child Theme Creation: Set up theme inheritance structure
- Asset Organization: Plan CSS, JavaScript, and image file structure
- Build Process: Configure compilation and optimization workflows
- Version Control: Establish theme development and deployment strategies
3. Theme Structure
app/design/frontend/Vendor/theme-name/
├── etc/
│ └── view.xml
├── media/
│ └── preview.jpg
├── web/
│ ├── css/
│ ├── js/
│ └── images/
├── registration.php
└── theme.xml
4. Layout Development
- Page Layouts: Create custom page layouts and page configurations
- Layout Updates: Implement layout XML modifications and customizations
- Block Customization: Customize and extend Magento's block classes
- Container Management: Organize content containers and responsive behavior
- Template Hierarchy: Plan template file organization and reusability
5. Styling Implementation
- Component Styling: Develop modular, reusable CSS components
- Responsive Breakpoints: Implement mobile-first responsive design
- Typography System: Create consistent typography scales and hierarchies
- Color Systems: Implement theme color variables and variations
- Animation & Interactions: Add smooth transitions and micro-interactions
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.
- 1mo ago First seen · 157 lines · 54 tokens per session scan A f8a898832bac
magento-theme-developer is a skill published in the GitHub repository maxnorm/magento2-agent-skills (31 stars, last pushed 9mo ago), licensed MIT. It adds 54 tokens to every session and 1,333 once invoked, about $0.0002 per session on Opus 5.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-frontend-dev
This skill should be used when the user asks to "create a Knockout.js component", "add a UI Component", "modify layout XML", "customize a template", "write LESS CSS", "style with the Magento UI library", "add a RequireJS module", "extend JavaScript", "customize checkout", or "modify the cart page". Covers Magento 2…
magento-hyva
Build Hyva theme templates, Alpine.js components, Tailwind CSS styles, and View Models for Magento 2. Use when developing frontend for Hyva-based Magento stores.
magento2-hyva-dev
This skill should be used when the user asks to "create a Hyvä theme", "set up a child theme", "build an Alpine.js component", "make this CSP-compliant", "add Tailwind CSS classes", "convert Luma to Hyvä", "migrate Knockout to Alpine", work on "Hyvä checkout" or "Hyvä React components", or handle "Tailwind…
shopify
Expert Shopify theme development guidelines for Liquid, Online Store 2.0, CSS, JavaScript, and UX best practices.
shopify-theme-development-guidelines
Expert Shopify theme development with Liquid, Online Store 2.0, and performance best practices.
shopify-theme-optimization
Theme speed and UX optimization — Core Web Vitals, Liquid code, image loading, mobile responsiveness.