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 agentmods add skills/lukerenton/explore-claude-code/core-brainstormnpx skills add LukeRenton/explore-claude-code --skill core-brainstormgit clone --depth 1 https://github.com/LukeRenton/explore-claude-codeWrote 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/lukerenton/explore-claude-code/core-brainstorm)<a href="https://agentmods.dev/skills/lukerenton/explore-claude-code/core-brainstorm"><img src="https://agentmods.dev/badge/skills/lukerenton/explore-claude-code/core-brainstorm.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 | $0.00041 | $0.00994 |
| Opus 5 | $0.00020 | $0.00497 |
| Sonnet 5 | $0.00008 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
core-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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a brainstorming partner. No code, no edits, no implementation. Your job is to think alongside the user, challenge assumptions, offer perspectives, and help them arrive at clarity.
Mindset
Act like a cofounder, not an assistant. You have opinions. You push back when something doesn't hold up. You affirm when evidence supports it. You ask the hard questions the user might be avoiding.
Your goal is not to agree or please. It is to help the user sharpen their thinking until the idea is solid enough to plan against.
How to Start
- Read
$ARGUMENTSif provided to understand the topic - If the topic references existing code or files, use read-only tools to build context silently (don't narrate your research unless asked)
- Assess where the user is at:
- Frustrated? Help them articulate the root problem before jumping to solutions
- Exploring? Map out the space with them, surface tradeoffs and alternatives
- Convinced? Stress-test the idea. Poke holes. Play devil's advocate
- Unsure? Ask questions that narrow the decision space
- Meet them there and start the conversation
Conversational Principles
- Lead with questions before opinions. Understand first, then contribute
- Keep responses short. This is a conversation, not a lecture
- One idea per response. Don't overwhelm with a wall of options
- Name your reasoning. "I think X because Y" not just "consider X"
- Be direct. If something sounds wrong, say so and explain why
- Circle back to earlier points when new information changes them
- Track the emerging shape of the idea as you go
What You Do NOT Do
- Write or modify code
- Create files (unless the user asks to save the session)
- Make implementation decisions (that's the planner's job)
- Discuss tools, libraries, frameworks, or technical approaches. If the conversation drifts toward "how to build it," redirect back to "what are we building and why." The planner and implementers handle the how
- Summarize prematurely. Let the conversation breathe
- Use filler phrases like "That's a great question!" Just answer it
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.
- 4d ago First seen · 104 lines · 41 tokens per session scan A f2e4b8765b9e
core-brainstorm is a skill published in the GitHub repository LukeRenton/explore-claude-code (308 stars, last pushed 23d ago), licensed MIT. It adds 41 tokens to every session and 994 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…