Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Lykhoyda/ask-llm/plugin install ask-llmWrote 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/lykhoyda/ask-llm/brainstorm-all)<a href="https://agentmods.dev/skills/lykhoyda/ask-llm/brainstorm-all"><img src="https://agentmods.dev/badge/skills/lykhoyda/ask-llm/brainstorm-all.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.1 | $0.00056 | $0.00527 |
| Opus 5 | $0.00028 | $0.00264 |
| Sonnet 5 | $0.00011 | $0.00105 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
brainstorm-all 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 8d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portable contract
Apply the brainstorm contract with all five external providers: Gemini, Codex, Grok, Ollama, and Antigravity. The current host model forms its independent view first; unavailable providers are reported, not silently omitted; synthesis distinguishes verified evidence from inference.
Host adapters
Pi adapter
Follow /skill:brainstorm semantics with ask-multi providers gemini,codex,grok,ollama,antigravity, after the current Pi host model has committed its independent view.
Claude Code adapter
The existing detailed workflow below is the Claude Code adapter. Its Agent, MCP, hook, CLAUDE_PLUGIN_ROOT, and AskUserQuestion mechanics apply only on Claude Code; they do not override the Pi adapter above.
Multi-LLM Brainstorm (All Providers)
Consult all available external LLM providers (Gemini, Codex, Grok, Ollama, Antigravity) simultaneously while Claude Opus performs its own independent research on the topic, then synthesize perspectives from all six participants.
Instructions
-
Determine the brainstorm topic:
- If the user provided a topic directly, use it
- If the context is about code changes, gather the relevant diff with
git diffandgit diff --cached - If the context is a design/plan, gather the relevant documentation or conversation context
-
If no topic is clear, ask the user what they'd like to brainstorm about.
-
Launch the
brainstorm-coordinatoragent with the topic, external providers set togemini,codex,grok,ollama,antigravity, and any gathered context. The coordinator will:- Run its own Claude Opus research phase in parallel with the external dispatches (Phase 3B — reads actual files, traces code, uses WebFetch/WebSearch on referenced external docs)
- Dispatch the topic to the five external providers in parallel (Phase 3A)
- Synthesize all findings with Claude's verified findings weighted higher than inferred ones
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.
- 8d ago First seen · 44 lines · 56 tokens per session scan A 2bd1a47358b6
brainstorm-all is a skill published in the GitHub repository Lykhoyda/ask-llm (17 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 527 once invoked, about $0.0003 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-30.
Other skills, from other repositories
skill-provenance
Version, validate, package, verify, recover, and hand off Agent Skill bundles across local folders, registries, platform uploads, and agent sessions. Use for MANIFEST.yaml, CHANGELOG.md, bundle hashes, stale evals, frontmatter portability, derived skill packages, or version identity that must survive filename changes…
bootstrap
Add version tracking to an existing unversioned skill bundle. Use when you have a skill project with SKILL.md but no MANIFEST.yaml, no version headers, and no changelog. Creates the initial manifest, adds version metadata to files, and generates the first changelog entry. Triggers on: "bootstrap this skill", "add…
close
Update version tracking when finishing work on a skill bundle. Use when you're done editing a skill project and need to bump version headers, recompute manifest hashes, update the changelog, flag stale files, or prepare a commit message. Triggers on: "close the session", "update versions", "save the bundle", "I'm done…
validate
Run a focused validation check for a skill bundle. Use when the user asks to validate, verify hashes, check MANIFEST.yaml, confirm files are present, or distinguish a canonical bundle from a derived install or registry copy without opening or closing a full editing session.
open
Verify a skill bundle's integrity when opening a project. Use when loading a skill project directory and you need to check file completeness, verify SHA-256 hashes against MANIFEST.yaml, detect stale files, review recent changes, or understand what state the bundle is in before starting work. Triggers on: "open this…
handoff
Generate a handoff note summarizing skill project state for a future session or collaborator. Use when crossing a non-persistent boundary (e.g., Chat upload), ending a session that made significant decisions, or when the user explicitly asks for a handoff note. Triggers on: "generate a handoff", "write a handoff…