kolea: Command for Claude Code

.claude/commands/build-loop.md

build-loop is a command for Claude Code from robconery/kolea. It costs 21 tokens per session (936 once invoked), scanned A, original, MIT.

A command that follows a checklist in PLAN.md, sending each task to a builder and reviewer before committing it to Git. Git is a tool for tracking code changes.

In plain words
What is it for?
Use it to carry out an existing development plan one task at a time, with review and a commit after each approved task.
Why use it?
It prevents unchecked tasks from being skipped and keeps unreviewed or overly coupled changes out of the codebase.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter; mentions subagents.

This is robconery/kolea's own configuration. It tells Claude Code how to work on kolea itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kolea configures →

Reuse

Borrowing it

Nothing to install: this file belongs to robconery/kolea. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/robconery/kolea/main/.claude/commands/build-loop.md
Clone the repo
git clone --depth 1 https://github.com/robconery/kolea

Made for: Claude Code.

Wrote 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.

agentmods badge for build-loop

README.md
[![agentmods](https://agentmods.dev/badge/commands/robconery/kolea/build-loop/github.svg)](https://agentmods.dev/commands/robconery/kolea/build-loop)
Your own site
<a href="https://agentmods.dev/commands/robconery/kolea/build-loop"><img src="https://agentmods.dev/badge/commands/robconery/kolea/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.

agentmods 80×15 button for build-loop

Your own site · 80×15
<a href="https://agentmods.dev/commands/robconery/kolea/build-loop"><img src="https://agentmods.dev/badge/commands/robconery/kolea/build-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 936 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2mo ago against content hash befc783ef894, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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
Origin

Copies of this mod

2 near-identical copies found in the catalogue:

.claude/commands/build-loop.md · 85 lines

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

  1. Resolve the plan: use the path in $ARGUMENTS; else docs/PLAN.md; else stop and ask — do not infer a plan.
  2. Read it. It must be a checklist of tasks (- [ ] / - [x]). If it has no checkboxes, stop and report — it is not a build plan.
  3. 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:

  1. Build. Dispatch a builder subagent (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.

  2. Review. Dispatch a reviewer subagent (Agent tool, subagent_type: reviewer, model opus — reviewer must be ≥ builder). It invokes security-web and simplify, reads the builder's diff, and returns a verdict: PASS or FAIL with specific findings.

  3. Recurse. If FAIL: send the findings back to a fresh builder for the same task. Repeat build → review until PASS. No cap — a task is not done until it passes code and security review. Nothing reaches git history before PASS.

Read the full file on GitHub · 85 lines

Changes

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.

  1. 2mo ago First seen · 85 lines · 21 tokens per session scan A befc783ef894

Subscribe to this mod's changes

build-loop is a command published in the GitHub repository robconery/kolea (11 stars, last pushed 28d 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.