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/madebytokens/claude-brainstorm/forkgit clone --depth 1 https://github.com/MadeByTokens/claude-brainstormWrote 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/madebytokens/claude-brainstorm/fork)<a href="https://agentmods.dev/commands/madebytokens/claude-brainstorm/fork"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-brainstorm/fork.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.00023 | $0.00399 |
| Opus 5 | $0.00012 | $0.00199 |
| Sonnet 5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
fork 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 6d 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
1 near-identical copy found in the catalogue:
- fork — 100% identical, 0 lines differ
What it actually says
Fork Brainstorming Thread
The user wants to explore a tangent. Create a new branch in the brainstorming session.
Arguments
$ARGUMENTS contains the topic for the fork.
Actions to Perform
-
Update session state:
- Push current thread onto the thread stack
- Set current thread to the new fork name
- Add fork to the list of open forks
- Assign fork number (FORK 1, FORK 2, or nested like FORK 1.1)
-
Update session file:
- Add a separator line
--- - Add new section header:
## [FORK X] [topic name] - Add parent reference:
Parent: [previous thread]
- Add a separator line
-
Acknowledge the fork to user:
FORKED: "[topic]"
Parent: [previous thread name]
Exploring this tangent now. Use /brainstorm:back to return.
[Then immediately start brainstorming on this new topic - ask a provocative question or offer initial ideas]
Fork Numbering
- First fork from MAIN: FORK 1
- Second fork from MAIN: FORK 2
- Fork from FORK 1: FORK 1.1
- Fork from FORK 1.1: FORK 1.1.1
- etc.
Important
- Stay in brainstorming mode
- Immediately start generating ideas for the new fork topic
- Keep the same energy and rules as the main brainstorm
- Don't ask "are you sure?" - just fork and go
- Forks can be nested as many levels as needed
If No Topic Provided
If $ARGUMENTS is empty, ask:
"What tangent do you want to explore?"
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.
- 6d ago First seen · 57 lines · 23 tokens per session scan A d370313e6dae
fork is a command published in the GitHub repository MadeByTokens/claude-brainstorm (13 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 399 once invoked, about $0.0001 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 commands, from other repositories
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.