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.01208 |
| Opus 5.5 | $0.00006 | $0.00483 |
| Sonnet 5.5 | $0.00003 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
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 18d 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 — 72 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.
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. 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/apps/speckit-extension/commands/.
A node has to be in the step's _order.yml to reach the arm. The Companion arms dispatch /speckit-companion-<step>, whose body is assembled from nodes/<step>/_order.yml. A part added to a preset's own commands/ is inert for them: that body lands as the stock /speckit-<step> skill, which only the stock arm runs. Attaching a node for a bench means a file in nodes/<step>/ and its name in that step's _order.yml; the grep above is what proves it. If it is not there, the branch was not rebuilt (build.py) or not pushed. Stop and fix that first.
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.
- 18d ago Changed · +2 lines 561fad8b3e97
- 19d ago Changed · +10 lines e9adf4ab3a41
- 1mo ago Changed c9f2edd7ccad
- 1mo ago Changed 81476d97fa7a
- 1mo 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 (99 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 1,208 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-09-07.
Other commands, from other repositories
fest-commit
Commit changes with festival traceability metadata.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
mode
Show or switch the project's conformance mode between Enforced and À la carte, within the set the organization allows.
commit-push-pr
Commit, push, and open a PR (includes changeset creation).
util.gh-pr-content
Create pull request content from the current branch changes.
sync-branch
Sync feature branch with the latest main branch.