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 ports-and-adaptersgit 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/ports-and-adapters)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/ports-and-adapters"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/ports-and-adapters/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/ports-and-adapters"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/ports-and-adapters.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.00026 | $0.00366 |
| Opus 5.5 | $0.00010 | $0.00146 |
| Sonnet 5.5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
ports-and-adapters 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 23d 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.
This is a copy
80% identical to brainstorming — 40 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Ports And Adapters (Symfony)
Use when
- Domain rules must not depend on Doctrine, HTTP, or a vendor SDK.
- An infrastructure dependency (storage, payment, mail provider) must be swappable or faked.
- Structuring a bounded context into Domain, Application and Infrastructure layers.
Default workflow
- Model the domain in plain PHP: entities and value objects without ORM attributes.
- Declare ports as interfaces inside the domain, such as a repository interface.
- Write use cases in the application layer as commands and handlers that depend only on ports.
- Implement adapters in infrastructure (Doctrine repository, API client) and map entities outside the domain, with XML mapping.
- Bind each port to its adapter in the service configuration; controllers live in infrastructure.
Guardrails
- Nothing under
src/Domain/imports Symfony, Doctrine or vendor SDK classes. - Dependencies point inward: infrastructure knows the domain, never the reverse.
- Do not add the layers to a CRUD module with no business rules.
- Test the domain with plain unit tests and the adapters with integration tests.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- The layer layout and the port interfaces.
- The adapters and their service bindings.
- Domain unit tests that boot no kernel.
References
reference.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.
- 23d ago Changed · +2 lines 85fb7c609d44
- 1mo ago Changed · +2 lines · -3 tokens per session 3b02a65d6049
- 1mo ago First seen · 40 lines · 29 tokens per session scan A bb4564ec32f3
ports-and-adapters is a skill published in the GitHub repository dev-toolings/superpowers-symfony (227 stars, last pushed 23d ago), licensed MIT. It adds 26 tokens to every session and 366 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to brainstorming, differing in 40 lines, and is treated as a copy.
Other skills, from other repositories
architecture-paradigm-cqrs-es
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
spine-design
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
warden-harden
Produce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".
cortex-integrate
Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
spine-api
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".
backend-cqrs-patterns
Use this skill when the user says 'CQRS', 'command query segregation', 'separate read write model', 'command model', 'query model', 'read model', 'write model', 'materialized view', 'command handler', 'query handler'. This skill enforces: strict command/query separation, write model optimized for consistency, read…