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 Kocal/symfony-contribution-skills --skill symfony-code-contributiongit clone --depth 1 https://github.com/Kocal/symfony-contribution-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/kocal/symfony-contribution-skills/symfony-code-contribution)<a href="https://agentmods.dev/skills/kocal/symfony-contribution-skills/symfony-code-contribution"><img src="https://agentmods.dev/badge/skills/kocal/symfony-contribution-skills/symfony-code-contribution.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.1 | $0.00049 | $0.02606 |
| Opus 5 | $0.00024 | $0.01303 |
| Sonnet 5 | $0.00010 | $0.00521 |
| Haiku 4.5 | $0.00005 | $0.00261 |
Grade A, and why
symfony-code-contribution 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 8d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Activate
Use when writing, modifying, or reviewing PHP code for a contribution to Symfony core or any Symfony-maintained PHP package (bundles, UX PHP side, AI, Mailer, Messenger, Recipes' PHP, etc.).
Do not apply these rules to JavaScript/TypeScript projects such as Webpack Encore or the Stimulus/UX frontend assets — follow that project's own CONTRIBUTING and standards instead. For documentation (.rst) changes, use the symfony-docs-contribution skill.
Core Rules
- Run PHP CS Fixer before every commit. Most style below is auto-enforced by the project's
.php-cs-fixer.dist.php— never hand-format against it:php ./vendor/bin/php-cs-fixer fix -v. - Never break the backward-compatibility promise on a maintenance/minor branch. Public and protected APIs are frozen: deprecate, never remove or change signatures. Breaking changes land only on the next major branch.
- Target the right branch. Bug fixes -> oldest maintained branch that still has the bug (it merges up automatically). New features and deprecations -> current development branch. Never add a feature on a patch branch.
- Ship every deprecation complete, in the same PR: a
trigger_deprecation()call, an@deprecatedPHPDoc tag, aCHANGELOG.mdentry, and theUPGRADE-*.mdentries. - Add the MIT license header at the top of every new PHP file, before the
namespace. - One class per file. Add tests. Do not write PHPDoc that only restates the signature.
Coding Standards
The rules below are what PHP CS Fixer enforces and what reviewers check.
Formatting
- One space after each comma.
- One space around binary operators (
==,&&,||, ...) except concatenation (.). - Unary operators (
!,--,++) stick to their variable, no space. - No spaces around
[/]in array access:$a[0], not$a [0]. - Multi-line arrays: trailing comma after every item, including the last.
Control flow & returns
- Always brace control-structure bodies, even single statements.
- Blank line before
return, unless thereturnis alone inside a statement group (e.g. anif). - No
else/elseif/breakafter anif/casebranch that already returns or throws. return null;when returning null; barereturn;for void. Do not add avoidreturn type in tests.
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.
- 8d ago First seen · 159 lines · 49 tokens per session scan A a34874c81031
symfony-code-contribution is a skill published in the GitHub repository Kocal/symfony-contribution-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 2,606 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-08-31.
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 +…
symfony:daily-workflow
Daily development workflow for Symfony projects including common tasks, debugging, and productivity tips.
solid-php
Use when applying SOLID principles to Laravel 13 / PHP 8.3+ code — file size limits, interface placement, or PHPDoc enforcement.
laravel-migrations
Use when designing a database schema or managing Laravel 13 migrations — Schema Builder, columns, indexes, foreign keys, or seeders.