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/rhuss/cc-slidevWrote 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/rhuss/cc-slidev/brainstorm)<a href="https://agentmods.dev/commands/rhuss/cc-slidev/brainstorm"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/brainstorm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rhuss/cc-slidev/brainstorm"><img src="https://agentmods.dev/badge/commands/rhuss/cc-slidev/brainstorm.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.03045 |
| Opus 5.5 | $0.00006 | $0.01218 |
| Sonnet 5.5 | $0.00003 | $0.00609 |
| Haiku 4.5 | $0.00001 | $0.00304 |
Grade A, and why
slidev: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 1mo 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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming & Information Collection
Conduct interactive brainstorming session to gather ideas, research topic, and establish foundation for evidence-based presentation.
Approach: Focus on content research - gather ideas, research materials, and identify themes.
Prerequisites: Run /slidev:frame first to establish presentation parameters (duration, audience, etc.)
Note: This phase gathers raw material. Structure and refinement come later using evidence-based principles (see references/presentation-best-practices.md).
Execution
1. Check for Presentation Configuration
Check if presentation-config.md exists:
Use Read tool to check for presentation-config.md
If exists:
- Read it to extract parameters for context:
- Duration and target slide count
- Audience and skill level
- Presentation context
- Use these as constraints for research
If not exists:
- Inform user: "⚠️ No presentation config found. Run
/slidev:framefirst to establish parameters (duration, audience, etc.), or continue without constraints." - Ask: "Continue brainstorming without constraints?"
- If no: Exit and suggest running
/slidev:frame - If yes: Proceed (will need to frame later)
2. Gather Research Context
Use AskUserQuestion to collect research parameters:
Question 1: Title & Abstract
Ask user:
- Rough title idea: One-liner working title (can be revised later)
- Abstract (optional): CfP abstract, initial description, or main message
- If submitting to conference: paste full abstract
- If internal talk: brief description of what you want to cover
- If exploring: leave blank, we'll develop together
Question 2: Research Materials
Ask user what materials to review:
- Local materials:
- Directory path to review (e.g.,
./docs,./research) - Specific files (e.g.,
notes.md,outline.txt) - Or: "none" if starting fresh
- Directory path to review (e.g.,
- Web resources:
- URLs to documentation, articles, or videos
- Or: "none" if no specific URLs
- Keywords for research:
- Topics or concepts to research online
- Or: "none" to skip web research
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.
- 1mo ago First seen · 490 lines · 14 tokens per session scan A bf927db8bfd9
slidev:brainstorm is a command published in the GitHub repository rhuss/cc-slidev (54 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 3,045 once invoked, about $0.0001 per session on Opus 5.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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.