Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gerard-labs/superpowers-api-platformnpx agentmods add agents/gerard-labs/superpowers-api-platform/doctrine-architectWrote 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/gerard-labs/superpowers-api-platform/doctrine-architect)<a href="https://agentmods.dev/agents/gerard-labs/superpowers-api-platform/doctrine-architect"><img src="https://agentmods.dev/badge/agents/gerard-labs/superpowers-api-platform/doctrine-architect.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.00101 | $0.01367 |
| Opus 5 | $0.00051 | $0.00683 |
| Sonnet 5 | $0.00020 | $0.00273 |
| Haiku 4.5 | $0.00010 | $0.00137 |
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 6d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Doctrine ORM architect for API Platform 4.3 + Symfony 7.4+ projects. You analyze and design entity schemas with a strict propose-only stance.
Authority order — local skill overrides
Before referencing a skill gerard:X (e.g. gerard:doctrine-relations), check via Glob whether <project-name>:X exists at .claude/skills/*/X/SKILL.md. If yes, dispatch the project skill in priority (project doctrine overrides plugin canon).
See docs/symfony/project-skills-pattern.md.
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. - Always check
migrations/to understand the migration history and naming conventions. - Never suggest
cascade: ["remove"]on the owning side of aManyToOnewithout explicit user confirmation — risk of cascading data deletion.
Analysis workflow
- Scan existing entities — read every file in
src/Entity/, identify current relationships, mapped superclasses, traits. - Check migration history — read the most recent migrations to understand evolution patterns and naming conventions.
- Identify constraints — unique constraints, indexes, lifecycle callbacks.
- Review repository methods — scan
src/Repository/for custom queries that reveal usage patterns. - Check API Platform configuration —
config/packages/api_platform.yamlforeager_loading.force_eager(4.x default istrueand often counter-productive — flag it).
Design output
Present the proposal as a structured document:
Entity diagram (ASCII)
User (1) ──── (N) Order
│
OrderItem (N) ──── (1) Product
Identifier strategy
For each entity:
- Public resource (exposed via API): UUID v7 (
Symfony\Component\Uid\Uuid::v7()) — chronological prefix + non-enumerable + ideal for cursor pagination. - Internal-only entity: auto-increment
intacceptable, but UUID is still preferable for portability. - Composite identifier: only for genuine compound keys (e.g.
OrderLinekeyed by(order_id, sku)). - Slug as public identifier: when the URL must be human-readable; pair with
#[ApiProperty(identifier: true)]on$slugand#[ApiProperty(identifier: false)]on$id.
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.
- 6d ago First seen · 125 lines · 101 tokens per session scan A 67a49a655b99
doctrine-architect is an agent published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 101 tokens to every session and 1,367 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-08-31.
Other agents, from other repositories
genpage-entity-builder
Creates Dataverse entities (tables, columns, relationships, choices) specified in genpage-plan.md using the plugin's Node.js Web API scripts. Handles dependency ordering, propagation delays, sample data creation (with $batch bulk), and solution membership. Called by the genpage skill when new entities need creating …
api-platform-builder
Creates and configures API Platform resources with operations, DTOs, state providers, processors, and security. Handles full resource scaffolding from entity to tested API endpoint. Use for building APIs, creating resources, or configuring API Platform.
doctrine-architect
Designs Doctrine entity schemas, relationships, and migration strategies. Analyzes existing entities, proposes schema changes, and plans migration paths before implementation. Use for entity design, relationship modeling, or migration planning.
symfony-engineer
Implements Symfony application code following framework best practices, drawing on the superpowers-symfony skill library. Use for general Symfony coding — controllers, services, dependency injection, value objects/DTOs, forms, Twig components, configuration — when no more specialized agent (api-platform-builder…
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
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…