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 letitbk/claude-academic-setup --skill brainstorminggit clone --depth 1 https://github.com/letitbk/claude-academic-setupWrote 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/letitbk/claude-academic-setup/brainstorming)<a href="https://agentmods.dev/skills/letitbk/claude-academic-setup/brainstorming"><img src="https://agentmods.dev/badge/skills/letitbk/claude-academic-setup/brainstorming.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.00059 | $0.00995 |
| Opus 5 | $0.00030 | $0.00498 |
| Sonnet 5 | $0.00012 | $0.00199 |
| Haiku 4.5 | $0.00006 | $0.00100 |
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 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Designs
Overview
Help turn ideas into fully formed designs and specs through structured, interactive questioning using the AskUserQuestion tool.
Start by understanding the current project context, then conduct multiple rounds of questioning to deeply understand requirements before proposing designs.
The Process
Phase 1: Interactive Questioning (MANDATORY)
Use the AskUserQuestion tool repeatedly to conduct an interview-style session. This is not optional - always use this tool for questioning.
Question Categories
Use a mix of these question types across rounds:
Problem Understanding
- What problem are you actually trying to solve? (not what you asked for)
- What would "success" look like? How will you know this worked?
- What have you already tried? What didn't work?
Constraints & Boundaries
- What are the non-negotiables vs nice-to-haves?
- What are the boundaries (time, scope, resources)?
- What should this explicitly NOT do?
Context & Stakeholders
- Who else is affected by this? Who are the stakeholders?
- What's the broader context this fits into?
- What happens before and after this?
Edge Cases & Risks
- What's the weirdest/hardest case this needs to handle?
- What could go wrong? What are you worried about?
- What assumptions might be wrong?
Preferences & Style
- What's your style preference? (verbose vs minimal, etc.)
- What similar things do you like/dislike?
- What tradeoffs are acceptable?
"Why" Questions
- Why this approach vs alternatives?
- Why now? What triggered this?
- Why does this matter?
AskUserQuestion Tool Usage
Each round should use:
- 2-4 questions maximum - Don't overwhelm
- Clear, specific options when choices exist
- multiSelect: true when multiple answers make sense
Typical Flow
Round 1: Core Problem
- What are you trying to accomplish?
- Why is this needed now?
Round 2: Constraints & Context
- What are the hard constraints?
- Who/what else is involved?
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 · 138 lines · 59 tokens per session scan A af229d70a03b
brainstorming is a skill published in the GitHub repository letitbk/claude-academic-setup (43 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 995 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
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…