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 agentmods add skills/fusengine/agents/php-standardsnpx skills add fusengine/agents --skill php-standardsgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/php-standards)<a href="https://agentmods.dev/skills/fusengine/agents/php-standards"><img src="https://agentmods.dev/badge/skills/fusengine/agents/php-standards.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 | $0.00047 | $0.01362 |
| Opus 5 | $0.00023 | $0.00681 |
| Sonnet 5 | $0.00009 | $0.00272 |
| Haiku 4.5 | $0.00005 | $0.00136 |
Grade A, and why
php-standards 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 yesterday.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Includes composer.json and project-structure templates (src/ for library code, tests/ wired via autoload-dev, PSR-4 namespace mapping), and the core PER/PSR-1 file rules (4 spaces, LF endings, no closing ?>).
Do NOT use this skill for language syntax or feature questions — that is php-language-modern. Do NOT use it for Laravel-specific conventions, which live in the Laravel plugin.
PHP Standards (PSR / PER / Composer)
Agent Workflow (MANDATORY)
Before applying a standard, use TeamCreate to spawn 3 agents:
- fuse-ai-pilot:explore-codebase - Detect existing style config (
.php-cs-fixer.php,phpcs.xml),composer.jsonautoload - fuse-ai-pilot:research-expert - Verify a PSR's current status on php-fig.org before recommending it
- mcp__context7__query-docs - Cross-check composer.json schema
After changes, run fuse-ai-pilot:sniper for validation.
Overview
| Concern | Standard | Notes |
|---|---|---|
| Autoloading | PSR-4 | Recommended; PSR-0 is deprecated |
| Coding style | PER Coding Style 3.0 | "Extends, expands and replaces PSR-12"; PSR-12 remains the Accepted PSR |
| Logging | PSR-3 | LoggerInterface |
| Caching | PSR-6 / PSR-16 | Pool vs Simple Cache |
| HTTP | PSR-7 / 15 / 17 / 18 | Message / Handlers / Factories / Client |
| DI container | PSR-11 | ContainerInterface |
| Events | PSR-14 | Event Dispatcher |
| Time | PSR-20 | ClockInterface — testable "now" |
Critical Rules
- PSR-4 for autoloading, never PSR-0 - PSR-0 and
target-dirare deprecated. See psr4-autoloading.md. - PER Coding Style 3.0 is the current style spec - It supersedes PSR-12 in practice while requiring PSR-1. PSR-12 is still the officially Accepted PSR — document the nuance, don't pretend PSR-12 was withdrawn. See per-coding-style.md.
- Depend on PSR interfaces, not implementations - Type-hint
Psr\Log\LoggerInterface, not a concrete logger. - 4 spaces, no tabs; LF line endings; omit closing
?>- Core PER/PSR-1 file rules. src/for library code,tests/for tests - Wiretests/viaautoload-dev, neverautoload.
What ships with it
6 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.
- yesterday First seen · 108 lines · 47 tokens per session scan A e09a952caf35
php-standards is a skill published in the GitHub repository fusengine/agents (25 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,362 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
craftcms
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…
craft-php-guidelines
Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section headers…
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
building-telegram-bots
Writes correct, version-aware Telegram bot code. Use when writing, extending, or debugging a Telegram bot in python-telegram-bot, aiogram, grammY, or Telegraf. Not for Telegram client API (TDLib), languages other than Python and Node.js, or non-Telegram platforms.
php-cleanup
This skill should be used when the user asks to "find unused PHP code", "clean up dead code", "find unused Composer dependencies", "find unused imports", "remove dead PHP code", "run composer unused", "check for missing dependencies", "detect unused classes", "detect unused methods", "clean up use statements", "audit…
symfony-domain-modeling
Symfony domain modeling — entities, value objects, domain events, aggregates, domain exceptions. Triggers on: entity, value object, domain event, aggregate, domain exception, domain model, domain logic, business rule, invariant.