Borrowing it
Nothing to install: this file belongs to tarlepp/symfony-flex-backend. 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/tarlepp/symfony-flex-backend/master/AGENTS.mdgit clone --depth 1 https://github.com/tarlepp/symfony-flex-backendWrote 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/tarlepp/symfony-flex-backend/agents-md)<a href="https://agentmods.dev/instructions/tarlepp/symfony-flex-backend/agents-md"><img src="https://agentmods.dev/badge/instructions/tarlepp/symfony-flex-backend/agents-md/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/instructions/tarlepp/symfony-flex-backend/agents-md"><img src="https://agentmods.dev/badge/instructions/tarlepp/symfony-flex-backend/agents-md.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.01648 | $0.01648 |
| Opus 5.5 | $0.00659 | $0.00659 |
| Sonnet 5.5 | $0.00330 | $0.00330 |
| Haiku 4.5 | $0.00165 | $0.00165 |
Grade A, and why
symfony-flex-backend 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 today.
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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What is this?
Repository-specific instructions for AI coding agents working on this Symfony JSON REST API. Keep these instructions aligned with the established AI guidance and the actual code, dependency manifests, and CI workflows.
Table of Contents ᐞ
Project context ᐞ
- Before changing framework-dependent code, check
composer.jsonfor the PHP and Symfony versions and available packages, andsymfony.lockfor Flex recipes. Do not rely on remembered versions or assume an uninstalled component is available. - This repository is a JSON REST API using Doctrine ORM, migrations, Symfony Serializer and Validator, Security, and Twig. API Platform, Messenger, and Lock are not current architectural assumptions; verify dependencies and configuration before using any component.
- Treat the existing implementation, tests, configuration, and CI as the source of truth when documentation conflicts with behavior.
Architecture and Symfony conventions ᐞ
- Follow the resource-based REST architecture: entities in
src/Entity/, repositories insrc/Repository/, resources insrc/Resource/, DTOs insrc/DTO/, and REST controllers insrc/Rest/. - Keep business logic in resources or services and controllers thin. Custom
controllers in
src/Controller/generally use one__invokeaction per endpoint. The trait-based controllers insrc/Rest/are an established exception. - Use DTOs for API input and output rather than exposing entities. Reuse the
AutoMapper in
src/AutoMapper/and existing request value resolvers for mapping and request binding. - Follow the existing repository patterns and extend
BaseRepositoryfor new repositories. Prefer extending existing resources and services over adding parallel abstractions. - Use Symfony attributes and components where they fit the existing patterns. Preserve established configuration and routing conventions rather than imposing blanket rules or hand-writing framework infrastructure.
- Add Symfony packages with Composer/Flex when a capability is needed and justified. Reuse existing dependencies first, review recipe-generated changes, and do not hand-edit bundle registration or base bundle configuration in place of a Flex recipe.
- Use constructor property promotion and
readonlyfor suitable DTOs and value objects. Do not mark servicesreadonlywhere lazy proxies may be used.
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.
- today Changed · +2 lines · +36 tokens per session 1e8bce722df4
- yesterday Changed · +5 lines · +83 tokens per session 05410fe56546
- 2d ago Changed · -2 lines · -22 tokens per session a4eca7b9f74d
- 8d ago Changed · +3 lines · +53 tokens per session c122f4ed0cac
- 17d ago First seen · 155 lines · 1,498 tokens per session scan A 41181698f6e5
symfony-flex-backend AGENTS.md is an instructions file published in the GitHub repository tarlepp/symfony-flex-backend (288 stars, last pushed yesterday), licensed MIT. It adds 1,648 tokens to every session, about $0.0066 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-10-10.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.