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 brainstorminggit 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/brainstorming)<a href="https://agentmods.dev/skills/dev-toolings/superpowers-symfony/brainstorming"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/brainstorming/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/brainstorming"><img src="https://agentmods.dev/badge/skills/dev-toolings/superpowers-symfony/brainstorming.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.00020 | $0.00398 |
| Opus 5.5 | $0.00008 | $0.00159 |
| Sonnet 5.5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
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 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- effective-context — 88% identical, 36 lines differ
- quality-checks — 83% identical, 44 lines differ
- twig-components — 81% identical, 40 lines differ
- ports-and-adapters — 80% identical, 40 lines differ
- cqrs-and-handlers — 78% identical, 40 lines differ
What it actually says
Brainstorming (Symfony)
Use when
- A feature request is still vague and the requirements are not settled.
- Several designs are possible and the tradeoffs must be compared before choosing.
- You need to know which Symfony components a feature touches (entities, handlers, API resources, security, async) before planning.
- The decision must be made before a plan is written; once it is, hand off to
writing-plans.
Default workflow
- Restate the goal in one sentence and list what is known, unknown and out of scope.
- Ask the open questions (users, data, permissions, failure cases) and note the answers.
- Map the feature onto Symfony components: entities, services and handlers, API resources, voters, messages.
- Propose two or three designs with their tradeoffs and recommend one.
- Record the chosen design, the rejected options and the open risks, then hand off to
writing-plans.
Guardrails
- Do not write code or a step-by-step plan here: brainstorming ends at a chosen design.
- Prefer the patterns already present in the project over new ones.
- Ask one question at a time instead of guessing a missing requirement.
- Keep rejected options in the notes so the decision stays auditable.
Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.
Output contract
- The goal, scope and answered questions.
- The components involved and the recommended design with its tradeoffs.
- Open risks, ready to feed
writing-plans.
References
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 · +3 lines 4d2a729211e4
- 1mo ago Changed · +2 lines · -3 tokens per session efd3bc2493ed
- 1mo ago First seen · 39 lines · 23 tokens per session scan A 69c33bf363d6
brainstorming is a skill published in the GitHub repository dev-toolings/superpowers-symfony (227 stars, last pushed 23d ago), licensed MIT. It adds 20 tokens to every session and 398 once invoked, about $0.0001 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 skills, from other repositories
test-run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.
vigil-instrument
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".
airflow-expert
Expert-level Apache Airflow orchestration, DAGs, operators, sensors, XComs, task dependencies, and scheduling. Use when the user mentions orchestration, DAGs, workflow, scheduling, or data pipeline, or when the task involves DAG Fundamentals, Task Dependencies and Branching, Dynamic Task Generation, or Operators and…
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
eurodns
Show or modify explicitly requested EuroDNS records, with current schema verification, GET-before-write, concrete previews, and whole-zone replacement approval.