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.
npx skills add dev-toolings/superpowers-symfony --skill doctrine-eventsgit 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/skills/dev-toolings/superpowers-symfony/doctrine-events)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/doctrine-events"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/doctrine-events/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/skills/dev-toolings/superpowers-symfony/doctrine-events"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/doctrine-events.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00418 |
| Opus 5 | $0.00017 | $0.00209 |
| Sonnet 5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
symfony:doctrine-events 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 10d 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.
What it actually says
Doctrine Events (Symfony)
Use when
- You need side effects on entity persistence (timestamps, slugs, search indexing, notifications).
- Migrating an
EventSubscriberInterfaceDoctrine subscriber to ORM 3. - Choosing between lifecycle callbacks, entity listeners, and global lifecycle listeners.
Default workflow
- Pick the narrowest mechanism: callback (one entity, no deps) → entity listener (one entity, needs services) → lifecycle listener (cross-cutting, all entities).
- Wire it with attributes (
#[ORM\HasLifecycleCallbacks],#[AsEntityListener],#[AsDoctrineListener]). - Type the event argument by its per-event class (
PostPersistEventArgs,PreUpdateEventArgs, …). - Verify the side effect fires with a targeted functional test against a real DB.
Guardrails
- ORM 3.0 removed
EventSubscriberInterfaceDoctrine subscribers — never reintroduce them. - Type-check the entity early in a global lifecycle listener (it fires for every entity).
- Never call
flush()inside a Doctrine event handler — it corrupts the in-flight unit of work. preUpdateis restricted: change fields only via$args->setNewValue(), never touch associations.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open
reference.mdfor the three mechanisms, the event-args matrix, and migration from subscribers.
Output contract
- Listener/callback class with the correct attribute.
- Justification for the chosen mechanism.
- Validation outcomes (test that the side effect fired).
References
reference.mddocs/complexity-tiers.md
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 45 lines · 35 tokens per session scan A fde0a1ff3c8a
symfony:doctrine-events is a skill published in the GitHub repository dev-toolings/superpowers-symfony (210 stars, last pushed 9d ago), licensed MIT. It adds 35 tokens to every session and 418 once invoked, about $0.0002 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-30.
Other skills, from other repositories
ccc-pro-saas
Multi-tenant SaaS scaffolds: row-level security, billing, invitations · Pro tier only.
infrastructure
Use when creating infrastructure layer artifacts for a NestJS bounded context — Prisma repositories, in-memory repositories (testing), model mappers, NestJS module wiring, adapters (port implementations), or event handler infrastructure. Repository is pure persistence with no event dispatch.
api-platform-performance
Tune API Platform 4.3 + Doctrine + Symfony performance — recognize the 4.x default trap eagerloading.forceeager: true (often counter-productive, switch to false + targeted join fetches), use EXTRALAZY for large collections, project DTOs in DQL (NEW App\\Dto\\PostListItem(...)) to avoid hydrating full entities for list…
doctrine-batch-processing
Process large-volume Doctrine datasets (million-row imports, mass updates, ETL) without memory blowup. Use toIterable() + EntityManager::clear() per batch, partial hydration with DQL projection (NEW App\Dto\X(...)), HINTREADONLY when entities aren't mutated, MEMORYPEAKUSAGE tracking. Trigger on "iterate over all…
doctrine-fetch-modes
Tune Doctrine fetch modes to eliminate N+1 and over-hydration — LAZY (default), EXTRALAZY for huge collections (count(), contains() without load), EAGER per-property only with justification, partial hydration with addSelect(), IndexBy for O(1) lookups, HINTREADONLY. Covers the API Platform 4.x eagerloading.forceeager…
doctrine-transactions
Handle Doctrine transactions correctly — EntityManager::wrapInTransaction() for atomic multi-entity writes, doctrinetransaction Messenger middleware for command-bus atomicity, Doctrine\ORM\OptimisticLockException handling with #[Version] column, isolation levels, flush strategies (per-request vs explicit). Trigger…