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-run-all.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-run-all)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/bench-run-all"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/bench-run-all/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-run-all"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/bench-run-all.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.00016 | $0.01046 |
| Opus 5 | $0.00008 | $0.00523 |
| Sonnet 5 | $0.00003 | $0.00209 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
bench-run-all 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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task
The automated version of /bench-prep → run it → /bench-capture, for one size. Driver agents work the cells instead of a person.
Size from $ARGUMENTS (easy/medium/hard/oversized).
Faithful dispatch: a driver mimics the GUI, it does not follow raw command bodies. The bench is a trustworthy relative comparator with capture overhead isolated; it does not reproduce a human's absolute wall clock.
1. Check the cells
node ../speckit-bench/run-all.mjs --dry-run — if any cell is missing, run /bench-sync. Note the three versions it prints; they belong in the final report.
2. Prep
node ../speckit-bench/run-all.mjs prep --sizes <size> — resets the cells and writes their run markers into the harness.
3. Drive the three cells (Workflow, parallel)
One driver per cell (parallel of 3). Each works only in ~/dev/projects/conduit-<size>-<letter>, stamps startedAt/finishedAt into ../speckit-bench/runs-meta/conduit-<size>-<letter>.json (via date -u), and runs specify → plan → tasks → implement the GUI-faithful way (see ../speckit-bench/driver.mjs):
- For EACH step, prepend the same GUI preamble every arm gets —
buildStepPreamble(step, specDir)fromdriver.mjs, which imports the real renderer fromdist/ai-providers/promptPreamble.jsso it cannot drift — then dispatch the step's command.- stock arm → stock
/speckit.*command bodies. No capture script; stock is blind by design. - Companion arms →
/speckit.companion.*command bodies, and nothing on top of them. The bodies carry every capture call a run needs. A driver that also runscap.mjs <step> startwrites the start stamp twice — the second is a documented no-op that still costs a round-trip on every step, and it inflated wave A's call count by four. The count that matters comes from the writer's own.trace.jsonl, so the driver has no bookkeeping of its own to do.
- stock arm → stock
- After dispatching a step, wait for it to settle —
waitForSettle(cellDir, step)polls.spec-context.jsonuntil the step's completed status or any later one appears. It returnsfolded: truewhen the status overshot, which happens for two shipped reasons: the fast path folds specify/plan/tasks ontoready-to-implement, and mark-complete takes implement tocompleted. A folded step is already done — never re-dispatch it, and never steer the size verdict to make steps settle one at a time. Right-sizing is the feature under measurement; a driver that disables it produces numbers that look valid and are not. - Do not time the capture calls. The harness counts them from
.trace.jsonland the timing itself is under the noise floor.
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.
- 3d ago Changed · +15 lines · -5 tokens per session 1a0084ba0294
- 11d ago First seen · 34 lines · 21 tokens per session scan A a4567fe8e677
bench-run-all is a command published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,046 once invoked, about $0.0001 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-30.
Other commands, from other repositories
migrate-to-typescript
Migrate JavaScript project to TypeScript.
svelte:component
Create new Svelte components with best practices, proper structure, and optional TypeScript support.
autospec.plan
Generate YAML implementation plan from feature specification.
code-locate
Given a behavior description, locate candidate code paths and line ranges in the active codebase that probably implement it. Output up to 10 candidates with HIGH/MEDIUM/LOW confidence, one-line rationale per candidate, and an explicit search trail; propose a SOURCEOFTRUTH.md update so the next workflow step (typically…
harvest-session-learnings
Scan the current working session and the active task's artifacts for reusable, generalizable lessons (what was tried, what failed and why, what surprised us, what the next task should do differently) and propose anchored entries to append to the task's LEARNINGS.md, the produce-side counterpart to the ADR-0017 consume…
screen-spec
Generate a screen specification from a Figma frame using MCP tools (getdesigncontext, getscreenshot). Produces a spec doc matching the SCREENSPEC.md template with layout sketch, components used, spacing observed, data dependencies, copy, accessibility notes, interactions, and error states. Use when documenting a…