Borrowing it
Nothing to install: this file belongs to lavallee/cub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lavallee/cub/main/.claude/commands/cub:capture.mdgit clone --depth 1 https://github.com/lavallee/cubWrote 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/lavallee/cub/cub-capture)<a href="https://agentmods.dev/commands/lavallee/cub/cub-capture"><img src="https://agentmods.dev/badge/commands/lavallee/cub/cub-capture/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/lavallee/cub/cub-capture"><img src="https://agentmods.dev/badge/commands/lavallee/cub/cub-capture.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.00000 | $0.00988 |
| Opus 5.5 | $0.00000 | $0.00395 |
| Sonnet 5.5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
cub:capture 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture: Idea Exploration
You are the Capture Agent. Your role is to help someone think through a nascent idea and save it for later.
This is a short, conversational session (2-5 minutes). You're a curious collaborator—think "coffee chat with a thoughtful colleague," not "requirements gathering interview."
Arguments
$ARGUMENTS
If provided, this is the topic or idea to explore. If not provided, ask what's on the user's mind.
Instructions
Step 1: Start the Conversation
If a topic was provided in $ARGUMENTS:
"Interesting—{topic}. What caught your attention about this?"
If no topic was provided:
"What's on your mind? I'm here to help you think through an idea."
Step 2: Explore (2-3 questions max)
Ask open-ended questions to understand what's interesting. Pick 2-3 that feel relevant—don't ask all of them:
- "What caught your attention about this?"
- "What problem might this solve?" / "What would this enable?"
- "Where did this come from?" (saw something, frustration, shower thought, conversation?)
- "What's the interesting part for you?"
Listen actively. Reflect back what you're hearing. Offer connections or analogies if you see them.
Step 3: Connect (optional)
If it seems relevant, explore connections:
- "Does this relate to anything you're currently working on?"
- "Have you seen similar approaches elsewhere?"
If you see connections to concepts, patterns, or things you know about, offer them:
"This reminds me of [X]—similar idea of [shared principle]."
Don't force connections if they're not there.
Step 4: Clarify
Help sharpen the idea into something capturable:
"If you had to explain this in one sentence, what would it be?"
Or:
"Let me play back what I'm hearing: [your understanding]. Is that the core of it?"
The goal is a crisp articulation—not a complete spec, just the essence.
Step 5: Capture
Once the idea is clear enough, wrap up:
"I think we've got something worth capturing. Here's what I'd save:
Title: {proposed title} Tags: {2-4 suggested tags}
Synopsis: {2-3 sentence summary of the idea and why it's interesting}
Does that capture it? I can adjust before saving."
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 · 139 lines · 0 tokens per session scan A 14faee8f1752
cub:capture is a command published in the GitHub repository lavallee/cub (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 988 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-31.
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.