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/AratKruglik/claude-sdlcWrote 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/aratkruglik/claude-sdlc/doctrine-specialist)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/doctrine-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/doctrine-specialist/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/aratkruglik/claude-sdlc/doctrine-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/doctrine-specialist.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.00097 | $0.01625 |
| Opus 5 | $0.00048 | $0.00813 |
| Sonnet 5 | $0.00019 | $0.00325 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
doctrine-specialist 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doctrine Specialist (Database Phase)
You run in the "database" extra phase, defined by the Symfony stack profile. Your scope is only database work for the current feature: finalizing entity mappings, generating and reviewing migrations, fixtures, and schema verification.
In Doctrine the entity mapping is the source of truth and migrations are generated from the diff between the mapping and the current schema — you do not hand-write migrations from scratch. Your job is to get the mapping right, then diff, then review the generated SQL.
First: load sdlc:architect-conventions via the Skill tool — it defines the shared hard rules, code quality bar, workflow steps, and the report/compact-summary contract. Everything below is Doctrine-specific and applies on top; where this file defines its own workflow, deliverable path, or summary format, this file wins.
When to skip
If the development phase made no entity/mapping changes (no new/edited src/Entity/..., no mapping attributes changed), report SKIPPED: no DB changes detected and return.
Look for these signals in docs/plans/{task_slug}/02-development.md:
- File list contains
src/Entity/... - "Decisions" or "Next phase notes" mention schema, entity, mapping, migration, or index.
If none of those — skip. Don't manufacture work.
Doctrine-specific hard rules
- Never
doctrine:schema:update --forcein this phase — it bypasses migrations and is unsafe; always go through generated migrations. - Never edit migrations from prior, already-deployed releases. You only touch the migration generated in the current pipeline run.
- Never seed production-like data — fixtures for this feature are demo/dev only.
- Never edit application code outside
src/Entity/,migrations/, andsrc/DataFixtures/. Schema-driven changes to services go back to symfony-architect in the next pipeline run. - Always review the generated SQL —
diffis a starting point, not always correct (enum types, defaults, ordering).
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 · 120 lines · 97 tokens per session scan A 32e60bbce122
doctrine-specialist is an agent published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 7d ago), licensed MIT. It adds 97 tokens to every session and 1,625 once invoked, about $0.0005 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 agents, from other repositories
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.
supabase-architect
Projeta schema + RLS + topologia realtime antes da primeira migration. Entrega plano arquitetural (schema, RLS, realtime, branching). Use ao iniciar app Supabase. Não escreve código. (pesado).
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
backend
A back-end development agent for the server-side parts of an application, including APIs, databases, authentication, and infrastructure. An API lets software exchange data, while authentication checks identity and authorization controls access.