Borrowing it
Nothing to install: this file belongs to opagani/cassini-workshop. 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/opagani/cassini-workshop/main/.claude/commands/build-loop.mdgit clone --depth 1 https://github.com/opagani/cassini-workshopWrote 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/opagani/cassini-workshop/build-loop)<a href="https://agentmods.dev/commands/opagani/cassini-workshop/build-loop"><img src="https://agentmods.dev/badge/commands/opagani/cassini-workshop/build-loop/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/opagani/cassini-workshop/build-loop"><img src="https://agentmods.dev/badge/commands/opagani/cassini-workshop/build-loop.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.00021 | $0.00936 |
| Opus 5.5 | $0.00008 | $0.00374 |
| Sonnet 5.5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
build-loop scanned grade A 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
(one `curl` against `wrangler dev`, one `bun build` + invoke, one route This is a copy
100% identical to build-loop — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
build-loop
🎯 Design for change. Each task's diff should be small, local, and behind a stable seam. The reviewer fails work that couples modules or bloats blast radius — builder should pre-empt that.
Execute the build plan in $ARGUMENTS (default: docs/PLAN.md) one task at a
time. You are the orchestrator (the lead thread). You do not write feature
code or review it yourself — you dispatch and gate.
Scope
- IN: build each unchecked task, get it through review, commit it.
- OUT: planning, writing PLAN.md, authoring specs, refactor/refinement passes. This command consumes a plan; it does not author one.
Preflight
- Resolve the plan: use the path in
$ARGUMENTS; elsedocs/PLAN.md; else stop and ask — do not infer a plan. - Read it. It must be a checklist of tasks (
- [ ]/- [x]). If it has no checkboxes, stop and report — it is not a build plan. - Confirm a clean git working tree. If dirty, stop and report; do not build on top of uncommitted changes.
The loop
For each task still unchecked (- [ ]), in order, top to bottom:
-
Build. Dispatch a
buildersubagent (Agent tool,subagent_type: builder, model sonnet). Give it: the exact task text, the relevant section of PLAN.md, the files it owns, and an instruction to invoke the project's TypeScript + DB skills and run the existing specs (bun test/ project test command) before reporting back. The builder does not commit. -
Review. Dispatch a
reviewersubagent (Agent tool,subagent_type: reviewer, model opus — reviewer must be ≥ builder). It invokessecurity-webandsimplify, reads the builder's diff, and returns a verdict:PASSorFAILwith specific findings. -
Recurse. If
FAIL: send the findings back to a freshbuilderfor the same task. Repeat build → review untilPASS. No cap — a task is not done until it passes code and security review. Nothing reaches git history beforePASS.
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.
- 2mo ago First seen · 85 lines · 21 tokens per session scan A befc783ef894
build-loop is a command published in the GitHub repository opagani/cassini-workshop (0 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 936 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to build-loop, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
quick-push
Git add all, commit with Claude, and push to current/new feature branch.
gsd:undo
Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.
update-agentskills
Apply a reusable lesson to /.agentskills (rules/skills/templates/commands), backup + commit + push.
repo-docs
Generate and maintain agent-readable repository documentation from source, docs, and git history.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
precommit
Command "precommit" from vdutts7/skills-not-mcp, covering /precommit, usage and execution.