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 chadixearth/graphyloop --skill brainstorminggit clone --depth 1 https://github.com/chadixearth/graphyloopWrote 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/chadixearth/graphyloop/brainstorming)<a href="https://agentmods.dev/skills/chadixearth/graphyloop/brainstorming"><img src="https://agentmods.dev/badge/skills/chadixearth/graphyloop/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/chadixearth/graphyloop/brainstorming"><img src="https://agentmods.dev/badge/skills/chadixearth/graphyloop/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.00058 | $0.02365 |
| Opus 5.5 | $0.00023 | $0.00946 |
| Sonnet 5.5 | $0.00012 | $0.00473 |
| Haiku 4.5 | $0.00006 | $0.00236 |
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 1mo 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Designs (Continuation Mode)
Turn ideas into fully formed designs and specs through a single-pass continuation flow — not an interactive Q&A loop.
Explore project context, infer requirements from the request and context, state your assumptions explicitly, then present a complete design in ONE message. The user responds once: approve, redirect, or add info. No back-and-forth questioning.
Anti-Pattern: "This Is Too Simple To Need A Design"
Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
What Changed From Original Brainstorming
This is a continuation-mode override of the Superpowers brainstorming skill. The original uses an interactive Q&A loop (one question at a time, back-and-forth). This version eliminates that loop:
- Removed: "Ask questions one at a time" / "One question per message" / interactive clarifying loop
- Removed: "Offer visual companion" as a separate message + wait
- Removed: Section-by-section design presentation with approval after each section
- Kept: HARD-GATE (no implementation before approval)
- Kept: Explore project context first
- Kept: Propose 2-3 approaches with tradeoffs and recommendation
- Kept: Write design doc, spec self-review, user review, writing-plans transition
- Added: Infer requirements from context, state assumptions explicitly, present complete design in one message
Checklist
You MUST create a task for each of these items and complete them in order:
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.
- 1mo ago First seen · 156 lines · 58 tokens per session scan A de630d00452d
brainstorming is a skill published in the GitHub repository chadixearth/graphyloop (3 stars, last pushed 14d ago), licensed MIT. It adds 58 tokens to every session and 2,365 once invoked, about $0.0002 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-31.
Other skills, from other repositories
zeroshot
Use Zeroshot to prepare, run, observe, or troubleshoot explicit multi-agent software work locally or on Zeroshot Cloud. Apply when the user names Zeroshot, including 'zeroshot this' or 'zeroshot it' (this orchestrator, not one-shot prompting), or asks about its CLI; do not route ordinary local work into Zeroshot…
aikito
Operate Aikito workspaces and resources, including reading inbox notes, managing memory, skills, projects, MCP servers, subagents, and synchronization.
kirby-collections-and-navigation
Builds Kirby listings, pagination, search, filtering/sorting/grouping, and navigation menus. Use when implementing collection logic in templates/controllers/snippets.
kirby-panel-and-blueprints
Designs Kirby 6 blueprints and Panel UI, including reuse/extends, programmable blueprints, value/display fields and areas. Use when changing Panel schemas or migrating legacy sections.
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.
kirby-headless-api
Exposes Kirby content to headless clients using the API, KQL, and JSON representations. Use when building API endpoints, KQL queries, or headless frontends.