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-code-reviewergit 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-code-reviewer)<a href="https://agentmods.dev/skills/maxnorm/magento2-agent-skills/magento-code-reviewer"><img src="https://agentmods.dev/badge/skills/maxnorm/magento2-agent-skills/magento-code-reviewer/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-code-reviewer"><img src="https://agentmods.dev/badge/skills/maxnorm/magento2-agent-skills/magento-code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00067 | $0.01468 |
| Opus 5 | $0.00034 | $0.00734 |
| Sonnet 5 | $0.00013 | $0.00294 |
| Haiku 4.5 | $0.00007 | $0.00147 |
Grade A, and why
magento-code-reviewer 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 10d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 Code Reviewer
Elite code review expert specializing in modern code analysis, security vulnerabilities, performance optimization, and production reliability for Magento 2 applications. Follows Adobe Commerce best practices and Magento 2 Certified Developer standards.
When to Use
- Reviewing code before commits or pull requests
- Ensuring code quality and standards compliance
- Security vulnerability assessment
- Performance optimization review
- Architecture and design pattern validation
- Pre-deployment code quality checks
Magento 2 Coding Standards (CRITICAL)
PSR-12 & Magento Standards
- PSR-12 Compliance: Strictly enforce PSR-12 coding standards
- Magento Coding Standard: Verify compliance with
vendor/magento/magento-coding-standard/Magento2 - EditorConfig: Check project's
.editorconfigfor indentation (4 spaces), line endings (LF), encoding (UTF-8) - Opening Braces: Classes and methods must have opening braces on their own line
- No Tabs: Must use spaces, never tabs
Type Safety & Modern PHP
- Strict Types:
declare(strict_types=1);required- Classes: After copyright block, before namespace
- Templates: Same line as
<?phpopening tag
- Type Hinting: All parameters and return types must be type-hinted
- Constructor Property Promotion: Use with
readonlymodifier where appropriate - Strict Comparisons: Always use
===and!==(never==or!=)
Code Quality Checklist
-
declare(strict_types=1);present - All parameters type-hinted
- All return types type-hinted
- Constructor property promotion with
readonlyused where possible - No unused imports
- Strict comparisons used throughout
- No static methods without justification
- Constructor has PHPDoc with all
@paramannotations - Copyright header present
- Minimal comments (only critical ones)
Comment Standards
- Minimal Comments: Only critical comments should remain
- PHPDoc Requirements: Include only
@param,@return, and@throwsannotations - No Verbose Descriptions: Avoid lengthy method descriptions unless genuinely complex
- No Inline Comments: Flag explanatory inline comments for straightforward code
- Copyright Headers: Must be present in all files
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.
- 10d ago First seen · 168 lines · 67 tokens per session scan A 38d256b4de03
magento-code-reviewer is a skill published in the GitHub repository maxnorm/magento2-agent-skills (29 stars, last pushed 7mo ago), licensed MIT. It adds 67 tokens to every session and 1,468 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-code-review
This skill should be used when the user asks to "review this PR/MR", "review this merge request", "review this module", "audit this module before merge", "review this theme", "audit this theme PR", or wants a "full review before release". Orchestrates a PR/MR, module, theme, or full-project code review by running the…
ai-slop
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside…
woo-guard
Review generated or changed WooCommerce code — extensions, payment and shipping integrations, checkout customizations, and order/product logic — before it ships. Best used reactively after an agent writes, edits, or reviews code touching WooCommerce APIs: wcgetorder, wcgetorders, wcgetproduct, WC() cart or session…
vertical-retail
Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder…
vertical-restaurants
Domain-knowledge primer for the restaurants & hospitality vertical (dine-in, pickup, delivery). Gives architect and pm the vocabulary, non-obvious operating rules, must-model entities, and incumbent landscape so a restaurant-product spec isn't naive about modifiers, 86'd items, aggregator commissions, tip law, and…
magpie-dependency-audit
Read-only dependency vulnerability audit for one repository or a local checkout. Detects the project's dependency manager(s), runs the appropriate audit tool, surfaces patchable findings grouped by severity, and proposes upgrades for maintainer review. Never modifies manifests or lock files and never opens update PRs.