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 agentmods add skills/gerard-labs/superpowers-api-platform/brainstormingnpx skills add gerard-labs/superpowers-api-platform --skill brainstorminggit clone --depth 1 https://github.com/gerard-labs/superpowers-api-platformWrote 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/gerard-labs/superpowers-api-platform/brainstorming)<a href="https://agentmods.dev/skills/gerard-labs/superpowers-api-platform/brainstorming"><img src="https://agentmods.dev/badge/skills/gerard-labs/superpowers-api-platform/brainstorming.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 | $0.00000 | $0.00552 |
| Opus 5 | $0.00000 | $0.00276 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
brainstorming 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 4d 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
Brainstorming (pre-architecture)
Use when
- A story is too vague to feed
/architectdirectly - You want to explore requirements + alternatives before committing to a plan
- Multiple framings of the same feature exist; you want to pick one
- The "smallest next step" is unclear
Position: this skill is upstream of the pipeline. Output = refined story description suitable for
/architect <story>or/api-resource-pipeline <story>. Once the brainstorm converges, exit and feed the pipeline.
Default workflow
- Restate the story in your own words. Get explicit agreement on the goal.
- Surface invariants : what MUST be true at the end? (user-visible features + non-functional like perf, security, a11y).
- List alternatives : 2-3 ways to deliver the invariants. Compare on complexity / risk / time.
- Pick the smallest valuable slice : the smallest PR that surfaces the most risky hypothesis.
- Identify unknowns : what would falsify the design? Where are the spikes needed?
- Refine the story description — one paragraph, ready to feed
/architect.
Guardrails
- Stay upstream. Don't propose code, file paths, or skill dispatch — that's the architect's job.
- Time-box the brainstorm. If you can't refine the story in 10 prompts, the story is too big — split it.
- No premature pattern selection (CQRS vs simple service, DTO vs Object Mapper, etc.) — that's also the architect's decision.
Output contract
- A refined story description (1 paragraph) usable as
$ARGUMENTSof/architect. - A short list of explicit invariants + non-invariants ("nice to have" excluded).
- A note on the smallest valuable slice.
Progressive disclosure
- This file for the brainstorm flow
docs/complexity-tiers.mdfor sizing the brainstorm output
References
docs/complexity-tiers.mddocs/symfony/pipeline-overview.md— what happens after the brainstorm converges
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.
- 4d ago First seen · 47 lines · 0 tokens per session scan A 70467d2b3bd9
brainstorming is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 552 tokens. 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 skills, from other repositories
symfony:doctrine-events
React to Doctrine entity lifecycle in Symfony with attribute listeners (#[AsDoctrineListener]/#[AsEntityListener], ORM 3) and lifecycle callbacks.
symfony:api-platform-dto-resources
Map entities to API DTOs in API Platform v4 with the Symfony Object Mapper (#[Map], stateOptions) for decoupled input/output contracts.
symfony:api-platform-filters
Implement API Platform filters - v4 Parameters API (QueryParameter) and legacy.
symfony:api-platform-versioning
Evolve API Platform APIs via deprecation (deprecationReason/sunset, RFC 8594/9745), the recommended alternative to versioning; plus path/header strategies.
symfony:messenger-retry-failures
Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions).
symfony:symfony-messenger
Async message handling with Symfony Messenger; configure transports (RabbitMQ, Redis, Doctrine); implement handlers, middleware, and retry strategies.