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 commands/mistydew/tokenicode-deepseek-alpha/brainstormgit clone --depth 1 https://github.com/mistydew/tokenicode-deepseek-alphaWrote 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/commands/mistydew/tokenicode-deepseek-alpha/brainstorm)<a href="https://agentmods.dev/commands/mistydew/tokenicode-deepseek-alpha/brainstorm"><img src="https://agentmods.dev/badge/commands/mistydew/tokenicode-deepseek-alpha/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.00000 | $0.02814 |
| Opus 5 | $0.00000 | $0.01407 |
| Sonnet 5 | $0.00000 | $0.00563 |
| Haiku 4.5 | $0.00000 | $0.00281 |
Grade A, and why
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 3d 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- brainstorm — 100% identical, 0 lines differ
- trellis-brainstorm — 100% identical, 8 lines differ
- brainstorm — 100% identical, 0 lines differ
- brainstorm — 100% identical, 0 lines differ
- trellis-brainstorm — 95% identical, 21 lines differ
- brainstorm — 95% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 488 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm - Requirements Discovery (AI Coding Enhanced)
Guide AI through collaborative requirements discovery before implementation, optimized for AI coding workflows:
- Task-first (capture ideas immediately)
- Action-before-asking (reduce low-value questions)
- Research-first for technical choices (avoid asking users to invent options)
- Diverge → Converge (expand thinking, then lock MVP)
When to Use
Triggered from /trellis:start when the user describes a development task, especially when:
- requirements are unclear or evolving
- there are multiple valid implementation paths
- trade-offs matter (UX, reliability, maintainability, cost, performance)
- the user might not know the best options up front
Core Principles (Non-negotiable)
-
Task-first (capture early) Always ensure a task exists at the start so the user's ideas are recorded immediately.
-
Action before asking If you can derive the answer from repo code, docs, configs, conventions, or quick research — do that first.
-
One question per message Never overwhelm the user with a list of questions. Ask one, update PRD, repeat.
-
Prefer concrete options For preference/decision questions, present 2–3 feasible, specific approaches with trade-offs.
-
Research-first for technical choices If the decision depends on industry conventions / similar tools / established patterns, do research first, then propose options.
-
Diverge → Converge After initial understanding, proactively consider future evolution, related scenarios, and failure/edge cases — then converge to an MVP with explicit out-of-scope.
-
No meta questions Do not ask "should I search?" or "can you paste the code so I can continue?" If you need information: search/inspect. If blocked: ask the minimal blocking question.
Step 0: Ensure Task Exists (ALWAYS)
Before any Q&A, ensure a task exists. If none exists, create one immediately.
- Use a temporary working title derived from the user's message.
- It's OK if the title is imperfect — refine later in PRD.
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.
- 3d ago First seen · 488 lines · 0 tokens per session scan A 7c7731eda092
brainstorm is a command published in the GitHub repository mistydew/tokenicode-deepseek-alpha (367 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,814 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.