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 keithhegit/ultra-orchestration --skill ultra-brainstorminggit clone --depth 1 https://github.com/keithhegit/ultra-orchestrationWrote 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/keithhegit/ultra-orchestration/ultra-brainstorming)<a href="https://agentmods.dev/skills/keithhegit/ultra-orchestration/ultra-brainstorming"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-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/keithhegit/ultra-orchestration/ultra-brainstorming"><img src="https://agentmods.dev/badge/skills/keithhegit/ultra-orchestration/ultra-brainstorming.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.00074 | $0.00468 |
| Opus 5 | $0.00037 | $0.00234 |
| Sonnet 5 | $0.00015 | $0.00094 |
| Haiku 4.5 | $0.00007 | $0.00047 |
Grade A, and why
ultra-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 9d 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
Ultra Brainstorming
Use this skill to create a design-quality front end before planning or coding.
This is the main vNext upgrade inspired by obra/superpowers.
Hard Gate
Do not move to planning or implementation until you have:
- explored the project context
- clarified ambiguities one question at a time when needed
- proposed 2-3 approaches with tradeoffs
- presented a recommended design
- received explicit approval or resolved objections
If the task is truly tiny, compress the design. Do not skip it.
Workflow
- Explore the codebase, docs, recent diffs, and any existing specs.
- Assess whether the request is one bounded change or several independent subsystems. Decompose if needed.
- Ask one clarifying question at a time. Prefer multiple choice when useful.
- Propose 2-3 approaches with your recommendation first.
- Present the design in sections sized to the complexity.
- Write the approved spec artifact.
- Self-review for ambiguity, contradiction, and hidden scope creep.
- Hand off to
ultra-planning.
Preferred Outputs
At minimum produce:
- problem framing
- non-goals
- success criteria
- constraints
- proposed architecture or flow
- testing or verification intent
- open decisions or assumptions
If the repo uses OpenSpec, write into proposal.md, design.md, and
tasks.md under the relevant openspec/changes/<change-id>/ directory.
Quality Bar
- surface ambiguity instead of silently picking an interpretation
- prefer the simplest design that satisfies the request
- avoid speculative abstractions
- explicitly call out acceptance criteria that downstream planning will need
Read brainstorming-flow and then rely on
ultra-vnext-core for the shared contracts.
What ships with it
2 files 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.
- 9d ago First seen · 59 lines · 74 tokens per session scan A 8772b6a4a66c
ultra-brainstorming is a skill published in the GitHub repository keithhegit/ultra-orchestration (6 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 468 once invoked, about $0.0004 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 skills, from other repositories
gsd-plan-review-convergence
Cross-AI plan convergence - replan until review concerns are resolved.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…