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 dorayo/orchestrix-skills --skill brainstormgit clone --depth 1 https://github.com/dorayo/orchestrix-skillsWrote 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/dorayo/orchestrix-skills/brainstorm)<a href="https://agentmods.dev/skills/dorayo/orchestrix-skills/brainstorm"><img src="https://agentmods.dev/badge/skills/dorayo/orchestrix-skills/brainstorm/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/dorayo/orchestrix-skills/brainstorm"><img src="https://agentmods.dev/badge/skills/dorayo/orchestrix-skills/brainstorm.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.00036 | $0.00928 |
| Opus 5 | $0.00018 | $0.00464 |
| Sonnet 5 | $0.00007 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
brainstorm 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
Turn a rough intent into an agreed, sharp requirement and design through dialogue. This is the front of the funnel and the project's main direction gate.
Core principle: "Too simple to need a design" is where unexamined assumptions waste the most work. Every intent gets a design — short if simple, but always presented and approved.
HARD GATE: do not invoke any build skill, write code, or scaffold anything until the design is approved. (
accept: inline.)
Process
- Explore context. Read the relevant knowledge slices (
taste/*,architecture/*,registry/*— physical paths fromcore-config.yaml, default underknowledge/) and existing code before asking anything. - Scope check first. If the intent spans independent subsystems, say so and help decompose into sub-projects — each gets its own spec → stories → build. Don't refine details of something that should be split.
- Clarify, one question at a time. Purpose, constraints, success criteria. Prefer multiple-choice. Never batch questions while direction is still open — each answer shapes the next question. Batch-questionnaire branch: once direction is settled and what remains is ≥3 mutually independent detail questions, switch to ONE structured questionnaire instead of asking serially — every question gets concrete options plus a recommended default, so the human can answer the whole set in a single pass (in Claude Code, use AskUserQuestion). Never mix modes: direction questions are always serial, independent details are always batched.
- Propose 2–3 approaches with trade-offs; lead with your recommendation and why.
- Present the design in sections, scaled to complexity; confirm each section before moving on. Cover: behavior, data flow, error handling, testing.
- Apply YAGNI ruthlessly. Cut every feature the intent does not require.
Output: the spec
Write one file in the specs namespace (default docs/specs/<slug>.md):
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.
- 6d ago Changed · +3 lines 46bd66b24cb7
- 10d ago First seen · 98 lines · 36 tokens per session scan A bec8f4d9f2c1
brainstorm is a skill published in the GitHub repository dorayo/orchestrix-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 928 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…