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.
git clone --depth 1 https://github.com/MadeByTokens/claude-code-plugins-madebytokensWrote 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-code-plugins-madebytokens/done)<a href="https://agentmods.dev/commands/madebytokens/claude-code-plugins-madebytokens/done"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/done.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.00022 | $0.01013 |
| Opus 5 | $0.00011 | $0.00507 |
| Sonnet 5 | $0.00004 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
done 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 7d 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.
This is a copy
100% identical to done — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End Brainstorming Session
The user is ending their brainstorming session. Wrap up gracefully.
Actions to Perform
-
Run the end script to clear brainstorm state:
PLUGIN_PATH/scripts/end-session.shReplace
PLUGIN_PATHwith the actual path from the<brainstorm-plugin-path>tag in your context.Capture the SESSION_FILE path from the output - you'll need it for subsequent steps.
If the script returns
ENDED=0, inform the user there's no active brainstorm session and stop. -
Write final summary to session file
- Add a "## Final Summary" section at the end
- List key themes that emerged
- Note total number of ideas generated
- Note any forks that were explored
-
Display numbered idea list and ask user to pick top ideas
If no ideas were generated, skip to step 5 and note "No formal ideas captured" in the display.
Otherwise, display all ideas numbered (1, 2, 3...), then proceed to the Top Ideas Selection section below.
-
Generate summary file (unless user chose "Skip summary")
Create a file in the same directory as the session file. Name it by inserting
-summarybefore.md:- Session:
brainstorm-checkout-20260119-1530.md - Summary:
brainstorm-checkout-20260119-1530-summary.md
- Session:
-
Display session complete message (see Display Format below)
-
Offer next steps (see Next Steps section below)
Top Ideas Selection
Use the AskUserQuestion tool to let the user choose which ideas go in the summary:
{
"questions": [
{
"question": "Which ideas should go in the summary?",
"header": "Top ideas",
"multiSelect": false,
"options": [
{"label": "Pick for me", "description": "I'll select the 3-5 most promising ideas"},
{"label": "All ideas", "description": "Include all ideas in condensed form"},
{"label": "Skip summary", "description": "Don't generate a summary file"}
]
}
]
}
Note: AskUserQuestion always allows free-text input via "Other". If user selects "Other", they can enter specific idea numbers (e.g., "1, 3, 7").
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.
- 7d ago First seen · 143 lines · 22 tokens per session scan A 2afa21777259
done is a command published in the GitHub repository MadeByTokens/claude-code-plugins-madebytokens (2 stars, last pushed 7mo ago), licensed MIT. It adds 22 tokens to every session and 1,013 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to done, differing in 0 lines, and is treated as a copy.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.