Borrowing it
Nothing to install: this file belongs to alfredoperez/speckit-companion. 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/alfredoperez/speckit-companion/main/.claude/commands/bench-prep.mdgit clone --depth 1 https://github.com/alfredoperez/speckit-companionWrote 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/alfredoperez/speckit-companion/bench-prep)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/bench-prep"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/bench-prep/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/alfredoperez/speckit-companion/bench-prep"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/bench-prep.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.00010 | $0.00551 |
| Opus 5.5 | $0.00004 | $0.00220 |
| Sonnet 5.5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
bench-prep 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 19d 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.
What it actually says
Your task
Arm the three cells for one feature size so each can be run through the real SpecKit Companion extension. The cells are the run folders — there are no copies.
Paths
Shell state does not persist between Bash calls, so start each one with this line:
. .claude/sandboxes-env.sh && eval "$(node "$SANDBOXES_REPO"/bench/paths.mjs --sh)"
It sets $SANDBOXES_REPO (the sibling speckit-sandboxes checkout, whose bench/ folder is the harness) and $BENCH_CELLS_DIR (where the cells are baked). When you hand a path to an agent, expand it first: an agent gets the absolute path, never the variable.
1. Resolve the size
From $ARGUMENTS — easy | medium | hard | oversized. If missing, ask with AskUserQuestion (one question). Don't guess.
2. Arm the cells
node "$SANDBOXES_REPO"/bench/run-all.mjs prep --sizes <size>
This resets each cell to its git baseline, writes the run marker into the harness (never into the cell — the marker names the arm), and prints the paste-able prompt. It does not open editor windows; pass --open if you want one per cell.
3. Hand off
Relay the prompt block to the user, then tell them:
- The three cells for this size are
conduit-<size>-a,-band-cunder the cells directory ($BENCH_CELLS_DIR; give the user the expanded path). Which letter is which arm is deliberately not visible from inside a cell;node "$SANDBOXES_REPO"/bench/run-all.mjs --dry-runprints the mapping. - Run specify → plan → tasks → implement in each, through the extension. The stock arm shows no progress tracking — that is the point, it is the blind control.
- The three can run at the same time; the cells are isolated.
- When all three are done, run
/bench-capture <size>.
Do not drive the pipelines yourself — the user runs them. Your job ends after prep prints the instructions.
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.
- 19d ago Changed · +10 lines 757dac2303d9
- 1mo ago Changed · -2 lines · -9 tokens per session b81e0785c26a
- 1mo ago First seen · 34 lines · 19 tokens per session scan A a092bd4b0955
bench-prep is a command published in the GitHub repository alfredoperez/speckit-companion (99 stars, last pushed 6d ago), licensed MIT. It adds 10 tokens to every session and 551 once invoked, about $0.0000 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
debug
Debug code issues with systematic problem-solving and troubleshooting steps.
explain
Explain complex concepts in simple terms with examples and analogies.
zooza-setup
One-time Zooza setup — teaches Claude your business vocabulary so it understands your terms in every future session.
svelte:component
Create new Svelte components with best practices, proper structure, and optional TypeScript support.
enforce.playwright-typescript
Enforce repository-wide compliance with playwright-typescript.instructions.md.
peachflow:init
Initialize peachflow v3 for a project. Creates state file and graph structure. Can reconfigure an existing project.