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 ddtcorex/maestro-skills --skill magento2-code-reviewgit clone --depth 1 https://github.com/ddtcorex/maestro-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/ddtcorex/maestro-skills/magento2-code-review)<a href="https://agentmods.dev/skills/ddtcorex/maestro-skills/magento2-code-review"><img src="https://agentmods.dev/badge/skills/ddtcorex/maestro-skills/magento2-code-review/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/ddtcorex/maestro-skills/magento2-code-review"><img src="https://agentmods.dev/badge/skills/ddtcorex/maestro-skills/magento2-code-review.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.00181 | $0.01991 |
| Opus 5 | $0.00090 | $0.00996 |
| Sonnet 5 | $0.00036 | $0.00398 |
| Haiku 4.5 | $0.00018 | $0.00199 |
Grade A, and why
magento2-code-review 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 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.
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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 Code Review
Orchestrates a review at one of four scopes — PR/MR, module, theme, or whole
project — by calling the existing QA trio and magento2-dev-core at the
right scope, then merging their output into one report with one severity
scale. This skill does not reimplement any check the trio already owns.
Related Skills
REQUIRED BACKGROUND: Load magento2-dev-core first — its
references/severity-and-codes.md defines the severity scale and finding
codes this skill's report uses.
Invokes magento2-linter (style/static analysis), magento2-security-scan
(vulnerability scanning), and magento2-performance-audit (runtime/
infrastructure) at whichever scope is in play — see "Scope modes" below.
Theme scope additionally cross-references magento2-hyva-dev (CSP) and
magento2-frontend-dev (Luma build/verify); it does not duplicate their
content. Together with the trio, this forms the "QA quartet" — the four
skills expected to run before a release.
Scope modes
| Mode | Trigger phrase example | File list source |
|---|---|---|
| Full path | "review this module/project" | module/theme/app/code path, as today |
| Explicit file list | caller already knows which files | passed straight through |
| Local git diff | "review this PR", branch already checked out | git diff against a base ref |
| Remote fetch | "review MR !123 before I check it out" | On DSH: gitlab_get_mr_diff (+ gitlab_list_own_review_threads, gitlab_post_inline_comment) in one call. Elsewhere: GitHub MCP (pull_request_read, preferred for GitHub) / glab mr diff / gh pr diff — text-pattern checks only, see below |
On DSH: call
maestro_review_scope_split {diffStats:{files,addedLinesPerFile}, mode}→ {split:{quick,deep},reason,estimatedSavingsTokens}. Run quick checks only on quick files, full deep only on deep; inject reason into prompt. Otherwise: apply same extension/path table by hand and note split in review header.
Full mechanics, exact commands, and the remote-fetch limitation:
references/scope-modes.md.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 148 lines · 181 tokens per session scan A 07d5d7b8a21e
magento2-code-review is a skill published in the GitHub repository ddtcorex/maestro-skills (4 stars, last pushed today), licensed MIT. It adds 181 tokens to every session and 1,991 once invoked, about $0.0009 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-31.
Other skills, from other repositories
magento-code-reviewer
Reviews Magento 2 code for quality, security, performance, and compliance with PSR-12 and Magento coding standards. Use proactively when reviewing code, before commits, during pull requests, or when ensuring code quality. Enforces strict type declarations, proper dependency injection, security best practices, and…
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
triage
GitHub issue and PR investigator. Pulls open issues/PRs, classifies them, searches the codebase for root cause or reviews contributed code, proposes fixes with file:line references, and optionally implements fixes. Use for investigating GitHub issues and reviewing PRs; do NOT use for general code review unrelated to…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
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…