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 caravanglory/magehub --skill standards-codinggit clone --depth 1 https://github.com/caravanglory/magehubWrote 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/caravanglory/magehub/standards-coding)<a href="https://agentmods.dev/skills/caravanglory/magehub/standards-coding"><img src="https://agentmods.dev/badge/skills/caravanglory/magehub/standards-coding/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/caravanglory/magehub/standards-coding"><img src="https://agentmods.dev/badge/skills/caravanglory/magehub/standards-coding.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.00029 | $0.02653 |
| Opus 5.5 | $0.00012 | $0.01061 |
| Sonnet 5.5 | $0.00006 | $0.00531 |
| Haiku 4.5 | $0.00003 | $0.00265 |
Grade A, and why
standards-coding 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 2mo 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards
Activation
Use When
- The task is to write, refactor, or review Magento PHP code for coding standards, service contracts, repositories, strict types, PHPCS, or extension attributes.
- The task mentions Magento coding standard, Api interfaces, repository pattern, phpcs.xml, strict_types, or maintainability conventions.
Do Not Use When
- The task is purely operational, performance profiling, frontend Hyva migration, or database schema work with a more specific skill.
- The user explicitly wants a quick prototype and accepts non-production scaffolding.
Required Inputs
- Target module/path, project coding standard command, and whether the code is public API, internal service, model, controller, or setup code.
- Existing project conventions for service contracts, repositories, data interfaces, and static analysis.
Workflow
- Inspect nearby module code and project PHPCS/static-analysis configuration before changing style or architecture.
- Add strict types, explicit visibility, constructor injection, interface-oriented APIs, and repository boundaries consistent with the module.
- Keep refactors narrowly tied to the requested change; avoid opportunistic architecture rewrites.
- Run formatting, PHPCS, static analysis, or targeted tests appropriate to the touched files.
Guardrails
- Do not introduce service contracts or repositories for one-off internal code unless they remove real coupling or match project conventions.
- Do not change public interfaces without backward-compatibility review and downstream implementer impact. (approval required)
- Do not suppress PHPCS/static-analysis errors without a local justification.
Verification
- Run vendor/bin/phpcs --standard=Magento2 or the project equivalent for touched PHP/XML files.
- Run targeted PHPUnit/static-analysis commands when method signatures or service behavior change.
- Report any standard command that is unavailable in the current project.
Output Contract
What ships with it
5 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.
- 2mo ago First seen · 341 lines · 29 tokens per session scan A 87454119ca17
standards-coding is a skill published in the GitHub repository caravanglory/magehub (2 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 2,653 once invoked, about $0.0001 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-31.
Other skills, from other repositories
laravel-audit-architecture
Audit a Laravel application's architecture: boundaries, responsibility, coupling, duplication, and maintainability. Use when auditing architecture.
laravel-audit-conventions
Audit a Laravel application for framework conventions: anti-patterns, version-appropriate APIs, and misuse of framework features. Use when auditing Laravel conventions.
code-quality
PHP and Laravel code quality toolchain — static analysis with Larastan/PHPStan, code style enforcement with Pint, automated refactoring with Rector, baseline management for legacy codebases, and CI pipeline integration via GitHub Actions. Use this skill whenever the user asks to check code quality, fix linting errors…
php-best-practices
PHP modernization, refactoring, code review, and standards enforcement assistant for PHP 8.2+ projects. Use this skill whenever the user wants to modernize legacy PHP code, refactor messy classes or controllers, review code for smells and anti-patterns, enforce PSR-12 and strict typing standards, or integrate Rector…
wp-phpcs-coding-standards
Set up and run PHPCodeSniffer with the WordPress Coding Standards (WPCS) and PHPCompatibility on a plugin or theme. Covers the composer dev-dependencies and their exact (and confusingly-named) packages — squizlabs/phpcodesniffer, wp-coding-standards/wpcs, phpcompatibility/phpcompatibility-wp…
php-laravel
Modern PHP 8.2+ and Laravel patterns: architecture, Eloquent, queues, Pest testing. Use when asked to "write PHP", "build a Laravel app", "fix Eloquent query", "add a queue job", "write a Pest test", or mentions PHP, Laravel, Eloquent, Blade, artisan, or migrations.