Borrowing it
Nothing to install: this file belongs to Kocal/symfony-contribution-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kocal/symfony-contribution-skills/main/AGENTS.mdgit 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/instructions/kocal/symfony-contribution-skills/agents-md)<a href="https://agentmods.dev/instructions/kocal/symfony-contribution-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/kocal/symfony-contribution-skills/agents-md.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.00521 | $0.00521 |
| Opus 5 | $0.00260 | $0.00260 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
symfony-contribution-skills AGENTS.md 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- symfony-contribution-skills GEMINI.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributing to Symfony
This project provides agent skills for contributing to Symfony. Two skills help you follow the project's official rules when you open a pull request.
Which skill to use
- Writing or reviewing PHP for Symfony core, a bundle, UX (PHP side), AI, etc. -> use the
symfony-code-contributionskill - Writing or editing
.rstdocumentation for symfony-docs or a package's docs -> use thesymfony-docs-contributionskill - A JS/TS project like Webpack Encore -> these skills don't apply; follow that project's own
CONTRIBUTING
Key rules (code)
- Run PHP CS Fixer before committing:
php ./vendor/bin/php-cs-fixer fix -v. Don't hand-format against it. - Never break the backward-compatibility promise on a maintenance/minor branch: deprecate, never remove or change public/protected signatures.
- Target the right branch: bug fixes -> oldest maintained branch that has the bug; features and deprecations -> current development branch.
- Ship every deprecation complete in one PR:
trigger_deprecation()+@deprecatedPHPDoc +CHANGELOG.md+UPGRADE-*.md. - Build exception messages with
sprintf(), capital first letter and trailing period,get_debug_type()for class names, double quotes (not backticks) around technical elements. - On a patch branch, fix the bug and nothing else: no new features, classes, config options, or deprecations.
- Naming:
camelCasemembers,UpperCamelCasetypes,SCREAMING_SNAKE_CASEconstants,snake_caseconfig/routes/Twig.
Key rules (docs)
- American English, second person ("you"), gender-neutral (they/them).
- reStructuredText, not Markdown: double backticks for inline code, list markers flush at column 0.
.. code-block:: <lang>for code; heading underline characters by level:=-~.".- Wrap prose at ~80 characters; define hyperlinks at the bottom of the page, not inline.
- Avoid these words: basically, clearly, easy/easily, just, obviously, of course, simply, trivial.
- Realistic examples:
Acmevendor,example.comdomains, nofoo/bar.
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.
- 7d ago First seen · 31 lines · 521 tokens per session scan A c73e4dd164d2
symfony-contribution-skills AGENTS.md is an instructions file published in the GitHub repository Kocal/symfony-contribution-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 521 tokens to every session, about $0.0026 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.