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/madarauchiha-314/the-loop/brainstormgit clone --depth 1 https://github.com/MadaraUchiha-314/the-loopWrote 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/madarauchiha-314/the-loop/brainstorm)<a href="https://agentmods.dev/commands/madarauchiha-314/the-loop/brainstorm"><img src="https://agentmods.dev/badge/commands/madarauchiha-314/the-loop/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.00033 | $0.00610 |
| Opus 5 | $0.00016 | $0.00305 |
| Sonnet 5 | $0.00007 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
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 5d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
the-loop: brainstorm $ARGUMENTS
Create a brainstorm.md scratchpad for a fuzzy idea that isn't ready to be pinned down
as requirements yet. Brainstorming is the optional Phase 0 of the loop and the root
artifact every later artifact derives from: brainstorm → requirements → design → tasks → implementation. If the work is already clear, skip this and go straight to
/the-loop:new-requirement.
Read the the-loop skill and reference/workflow.md first (phases, the
gate-owned-lock principle, reviews).
Steps
-
Create a temporary spec folder. Slugify
$ARGUMENTS→<slug>and createdocs/specs/draft-<slug>/(the-loop's convention for a spec with no ticket yet;/the-loop:create-ticketlater renames it todocs/specs/<id>/). Reuse the folder if it already exists. -
Write
brainstorm.mdfrom${CLAUDE_PLUGIN_ROOT}/skills/the-loop/templates/brainstorm.md(${CLAUDE_PLUGIN_ROOT}= the installed plugin's root; same in Cursor): problem / opportunity, context & constraints, ideas & options, sketches, open questions, and a working hypothesis. Keep it free-form — this is a scratchpad, not a spec. Set front-matterphase: brainstorming,status: draft,workItem: draft-<slug>, and thecollaboratorsyou want to think with. -
Iterate with feedback until it converges. The brainstorm is meant to change: gather feedback (interactively or via ticket comments — paper trail), refine the options, and resolve the open questions. The brainstorm has no approval gate (issue-281): never set
status: approvedor ask for a sign-off — it has converged when its author says the direction is settled, on the record. -
Point to the next step: convert the converged brainstorm into requirements with
/the-loop:new-requirement <title>(it reads the siblingbrainstorm.mdand derivesrequirements.mdfrom it), then/the-loop:create-ticketto mint the ticket.
Do not write requirements.md here — that is /the-loop:new-requirement. Brainstorming
stays exploratory; the moment you're asserting acceptance criteria you've left this phase.
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.
- 5d ago First seen · 45 lines · 33 tokens per session scan A 2c664489b1ed
brainstorm is a command published in the GitHub repository MadaraUchiha-314/the-loop (4 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 610 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-31.
Other commands, from other repositories
receipts
Find the receipt. A dated line, or it did not happen.
ship
Seen on their staging, then live. Rollback you have run.
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
import
Import a shared context bundle, or take a teammate's newer copy of one you already have.
extensions
Show what the connected context expects to reach, and whether this machine provides it.
list
List the NeatContext contexts you can connect.