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/jpm1118/threadwork/brainstormingnpx skills add JPM1118/Threadwork --skill brainstorminggit clone --depth 1 https://github.com/JPM1118/ThreadworkWhat 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.00000 | $0.01399 |
| Opus 5 | $0.00000 | $0.00700 |
| Sonnet 5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
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 2d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Skill
Explore a problem space and produce a design document that can inform implementation planning.
When to Use This Skill
Use this skill when:
- Starting work on a new feature with unclear requirements
- Exploring different implementation approaches
- Need to understand existing code before planning changes
- Want to document design decisions before coding
Purpose
Brainstorming is the discovery phase before planning. The output is a design document that:
- Captures the problem being solved
- Documents constraints and requirements
- Explores implementation approaches
- Makes key design decisions
- Prepares for the planning phase
Skill Workflow
Step 1: Understand the Request
Clarify with the user:
- What problem are we solving? (the "why")
- What are the constraints? (time, compatibility, dependencies)
- What does success look like? (acceptance criteria)
- Are there existing patterns to follow? (codebase conventions)
Step 2: Explore the Codebase
Investigate relevant areas:
# Find related files
find . -name "*.ts" | xargs grep -l "{relevant_term}"
# Understand existing patterns
cat src/{relevant_directory}/
# Check for existing tests
ls -la src/**/__tests__/
Document what you find:
- Existing implementations to follow
- Patterns used in the codebase
- Potential conflicts or integration points
- Technical constraints
Step 3: Consider Approaches
For each viable approach, evaluate:
| Criteria | Approach A | Approach B | Approach C |
|---|---|---|---|
| Complexity | |||
| Risk | |||
| Maintainability | |||
| Performance | |||
| Time to implement |
Step 4: Make Decisions
For each key decision point:
- State the question
- List the options
- Explain the trade-offs
- Make a recommendation (or ask for user input)
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.
- 2d ago First seen · 266 lines · 0 tokens per session scan A 429035cefaa5
brainstorming is a skill published in the GitHub repository JPM1118/Threadwork (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,399 tokens. 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.
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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…