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-wave.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-wave)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/bench-wave"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/bench-wave/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-wave"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/bench-wave.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.00015 | $0.00850 |
| Opus 5 | $0.00008 | $0.00425 |
| Sonnet 5 | $0.00003 | $0.00170 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
bench-wave 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task
Bench one wave of the pipeline diet, start to finish, and record it. $ARGUMENTS is the wave letter (B), optionally followed by the branch; the branch defaults to pipeline-diet/wave-<letter lowercase>. The plan and the results table live in the vault at Projects/speckit companion/plans/pipeline-speed/Pipeline Speed Execution.md.
One bench at a time. Nothing else heavy runs on this machine until the row is recorded.
1. The wave has to reach the cell
The bench dispatches from the pinned worktree, not from this checkout. Point it at the wave's pushed commit and rebuild the preamble:
git -C ~/dev/GitHub/speckit-companion.worktrees/bench-main fetch -q origin
git -C ~/dev/GitHub/speckit-companion.worktrees/bench-main checkout -q --detach origin/<branch>
(cd ~/dev/GitHub/speckit-companion.worktrees/bench-main && npm run compile)
Then prove the wave's text is what the cell will get: pick one line the wave changed and grep for it in ~/dev/GitHub/speckit-companion.worktrees/bench-main/speckit-extension/commands/. If it is not there, the branch was not rebuilt (assemble-nodes.py, build-commands.py) or not pushed. Stop and fix that first.
2. Gates, in this checkout, on the wave branch
python3 speckit-extension/scripts/assemble-nodes.py --check
python3 speckit-extension/scripts/check-shape-parity.py
python3 speckit-extension/scripts/instruction-budget.py
python3 -m pytest speckit-extension/tests -q
npx jest
A red gate means the wave is not ready to bench. Say which one and stop.
3. Bake and prep
node ../speckit-bench/sync-templates.mjs --sizes hard --speckit keep --ext code --sweep "wave <letter>"
node ../speckit-bench/run-all.mjs prep --sizes hard --modes companion,companion-living
node ../speckit-bench/run-all.mjs --dry-run
The bake prints speckitExtBuild as code@<sha>; it must be the wave's commit. The dry run prints which letter is which arm: take the two letters that are not stock. Never pass the mapping itself anywhere.
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 First seen · 60 lines · 15 tokens per session scan A 47f9fc8a9c83
bench-wave is a command published in the GitHub repository alfredoperez/speckit-companion (89 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 850 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-09-07.
Other commands, from other repositories
fest-commit
Commit changes with festival traceability metadata.
sddp-implement
Command description: Implement the current feature tasks. Argument hint: [optional: phase or task to start from] Command category: feature-delivery Prerequisites: spec, plan, tasks, checklists:complete-if-present.
wrap
The session-scoped landing step after ship: flips board rows, merges the operator's own green PRs one at a time, checks deploys, tidies branches and worktrees, writes the activity line, calls /kit:retro when a shipped PR merged, and prints the skim-first report. Use when the operator says to wrap up or close out the…
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.
commit
Based on the above changes, create a single git commit for the staged changes.