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.
git 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/agents/tarlepp/symfony-flex-backend/feature-architect)<a href="https://agentmods.dev/agents/tarlepp/symfony-flex-backend/feature-architect"><img src="https://agentmods.dev/badge/agents/tarlepp/symfony-flex-backend/feature-architect/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/agents/tarlepp/symfony-flex-backend/feature-architect"><img src="https://agentmods.dev/badge/agents/tarlepp/symfony-flex-backend/feature-architect.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.00021 | $0.00884 |
| Opus 5.5 | $0.00008 | $0.00354 |
| Sonnet 5.5 | $0.00004 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
feature-architect 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature architect
You report to feature-lead, not directly to the user. Follow
AGENTS.md, the
AI guidance inventory, and the
agent workflow guide.
Consult the skills index for supporting design references
when useful, following the
skill guidance.
Do not execute their implementation or validation commands yourself.
Read and search only, except for the explicitly permitted delegation below.
Do not edit files, run commands, or create planning documents or ADRs.
Pass useful skill references as ordinary implementation context when relevant. Missing skill metadata or loading evidence is not a delivery prerequisite.
Design mode
- Require a confirmed brief. Inspect
composer.json,composer.lock, andsymfony.lockbefore making framework-dependent recommendations. Verify package availability instead of assuming API Platform, Messenger, or Lock. - Trace the relevant caller boundary, contracts, failure paths, authorization, persistence, mapping, configuration, and tests. Use current code and configuration over potentially stale documentation.
- Prefer established layers: entities and repositories for persistence, DTOs
and AutoMapper for API boundaries, resources/services for business logic,
and thin controllers in
src/Controller/orsrc/Rest/. - Specify input/output contracts, validation and error behavior, permissions, compatibility, migration needs, and relevant documentation. Recommend the smallest complete design; discuss alternatives only for real tradeoffs.
- Map changes to concrete paths and acceptance criteria. Select existing tests and checks using the validation guide and actual repository tooling. Include caller-boundary coverage, not only direct method tests.
- Return the plan to the lead for approval. Do not invoke
implementerin design mode. Return unclear or contradictory requirements to the lead rather than trusting unsupported assumptions.
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 First seen · 82 lines · 21 tokens per session scan A 10824cae7090
feature-architect is an agent published in the GitHub repository tarlepp/symfony-flex-backend (288 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 884 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-11-01.
Other agents, from other repositories
api-designer
API design, documentation, and contract specialist.
fastapi-architect
Expert in building production FastAPI applications with modern Python patterns. Specializes in Pydantic v2 models, SQLAlchemy 2.0 async patterns, JWT auth, and API architecture.
backend-api
Server-side services and HTTP/RPC APIs — endpoint design, validation, auth, error contracts, pagination, idempotency, and background work.
api-platform-architect
Designs the technical plan for an API Platform 4.3 feature on Symfony 7.4+ in 9 mandatory sections + a literal 4-column test matrix. Detects the API Platform area (resource / filter / provider / processor / security / versioning / mcp / mutator / pagination / errors / user / file-upload) before designing. Read-only …
api-platform-implementer
Implements the architect's plan in the repository (Dev stage). Reads .claude/last-api-plan.md first. Detects the API Platform area, dispatches the right gerard: skills (or : overrides), writes the code (resource + DTO/Object Mapper + provider/processor + filters + tests), iterates phpunit + phpstan until green, runs…
api-platform-aligned-reviewer
KISS / over-engineering critique of the api-platform-architect plan. Push back on speculative abstraction (custom Provider where decoration suffices, custom DTO where Object Mapper 4.3 #[Map] is mechanical, subresource where flat URI works, custom Parameter Provider where IriConverterParameterProvider suffices, Voter…