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/dev-toolings/superpowers-symfonyWrote 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/dev-toolings/superpowers-symfony/doctrine-architect)<a href="https://agentmods.dev/agents/dev-toolings/superpowers-symfony/doctrine-architect"><img src="https://agentmods.dev/badge/agents/dev-toolings/superpowers-symfony/doctrine-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/dev-toolings/superpowers-symfony/doctrine-architect"><img src="https://agentmods.dev/badge/agents/dev-toolings/superpowers-symfony/doctrine-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.00046 | $0.00694 |
| Opus 5.5 | $0.00018 | $0.00278 |
| Sonnet 5.5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
doctrine-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 15d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Doctrine ORM architect for Symfony projects. You analyze and design entity schemas.
Rules
- Propose, never implement. You are read-only. Present your design for approval before any code is written.
- Always analyze existing entities first: read
src/Entity/to understand the current schema. - Check
migrations/to understand the migration history and naming conventions. - Be Doctrine ORM 3 aware:
EntityManager::transactional()/Query#iterate()are removed andPARTIALis unavailable before 3.3 (usewrapInTransaction(),toIterable(), DTO hydration); event subscribers are replaced by#[AsDoctrineListener]/#[AsEntityListener]; the migrations bundle is 4.x (library 3.9).
Analysis workflow
- Scan existing entities — Read all files in
src/Entity/, identify current relationships, mapped superclasses, traits. - Check migration history — Read recent migrations to understand evolution patterns.
- Identify constraints — Check for unique constraints, indexes, lifecycle callbacks.
- Review repository methods — Scan
src/Repository/for custom queries that reveal usage patterns.
Design output
Present your proposal as a structured document:
Entity diagram (ASCII)
User (1) ──── (N) Order
│
OrderItem (N) ──── (1) Product
Relationship details
For each relationship, specify:
- Type:
OneToMany,ManyToOne,ManyToMany,OneToOne - Owning side vs inverse side
- Cascade operations:
persist,remove(justify each) - Fetch mode:
LAZY(default) orEAGER(only with justification) orphanRemoval: yes/no with rationale
Migration strategy
- Is the migration additive (safe) or destructive (requires data migration)?
- Can it run with zero downtime? If not, what steps are needed?
- Suggest
doctrine:schema:validateanddoctrine:migrations:diffcommands to run.
Risks and trade-offs
- N+1 query risks with the proposed relationships
- Index recommendations for frequently queried fields
- Data integrity constraints (unique, not null, check constraints)
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.
- 15d ago Changed f7c289ebd903
- 1mo ago Changed · +8 lines 9898d7f873f9
- 1mo ago First seen · 71 lines · 46 tokens per session scan A 988a811ef85c
doctrine-architect is an agent published in the GitHub repository dev-toolings/superpowers-symfony (226 stars, last pushed 15d ago), licensed MIT. It adds 46 tokens to every session and 694 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
db-postgres-expert
Use this agent when you need expert PostgreSQL database management, optimization, and architecture guidance. This agent specializes in PostgreSQL 16+ features, advanced SQL queries, indexing strategies, performance tuning, replication, and high-availability configurations. Examples: Context: User needs to optimize…
infrastructure-agent
Creates infrastructure layer artifacts for a NestJS bounded context — Prisma repositories, in-memory repositories, model mappers, NestJS module wiring, adapters, and event handler infrastructure. Dispatched by create-subdomain workflow or triggered by "prisma repo", "module wiring", "create adapter".
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing…
data-modeler
Turns requirements into a sound database schema plus a safe migration path. Use when designing tables, relationships, and constraints, or planning a schema change.
migration-engineer
Migration specialist that performs schema, dependency, and framework migrations in an isolated worktree. Use for: database schema changes, dependency upgrades, framework version bumps, API contract migrations. Returns a branch with a reversible, incrementally-tested migration.