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-experiment.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-experiment)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/bench-experiment"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/bench-experiment/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-experiment"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/bench-experiment.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.01131 |
| Opus 5 | $0.00008 | $0.00566 |
| Sonnet 5 | $0.00003 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade B, and why
bench-experiment scanned grade B with 1 finding 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
If it is missing, or if `ps aux | grep mds_stores` shows Spotlight busy, tell the user to run `sudo mdutil -i off ~/dev/projects` and wait for them. Do not start a round on a machine that is already struggling. How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your task
Run one complete round of the benchmark and report what changed. The user says "run an experiment and bench it" and expects the whole thing without being asked for details.
The harness lives in the sibling speckit-bench repo and the app it measures in conduit. Its README.md is the reference; this command is the procedure.
1. Name the sweep
$ARGUMENTS is what the experiment is testing. Turn it into a short label — "hook anchors", "living specs off", "fresh baseline". If there is nothing to name, use today's date and call it a baseline repeat, which is also useful: it is how the noise floor gets measured.
2. Check the machine first
Twelve clones of a React app are about 8GB of files Spotlight has never seen, and indexing them has taken this machine to a load average of 260. Before baking:
ls ~/dev/projects/.metadata_never_index || echo "MISSING"
If it is missing, or if ps aux | grep mds_stores shows Spotlight busy, tell the user to run sudo mdutil -i off ~/dev/projects and wait for them. Do not start a round on a machine that is already struggling.
3. Bake
npm run compile # the driver dispatches the GUI preamble from dist/
node ../speckit-bench/sync-templates.mjs --sizes easy,medium,hard,oversized --ext code --sweep "<label>"
--ext code measures the extension in COMPANION_DIR, which is what an experiment on unreleased work needs. Use --ext latest only when the question is explicitly about the published build.
The bake prints the three versions it recorded and fails loudly if any cell can read what it is. Report the versions; do not report the arm mapping unless asked, and never pass it to a driver or a judge.
4. Prep and drive
node ../speckit-bench/run-all.mjs prep --sizes easy,medium,hard,oversized
Then one driver per cell, all twelve at once, following step 3 of /bench-run-all — the same GUI preamble, the same settle-wait, capture for the Companion arms only, and the cell's letter, never its arm. Twelve drivers in parallel is fine; the round costs the slowest cell rather than the sum.
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.
- 5d ago First seen · 80 lines · 15 tokens per session scan B 6c4d541bc924
bench-experiment is a command published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,131 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
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…