Cookbooks

Each cookbook is one task, start to finish, with the prompt to paste into your coding agent and rb’s real output from running it.

Every cookbook gives you:

• the problem, in two sentences;
• Paste this into your agent: a short task for Claude Code, Codex, Cursor, or any agent that runs terminal commands;
• What you’ll see: rb’s output, exactly as it printed it;
• What rb did, step by step: the commands under the hood, so you can run them yourself;
• Why it matters, in one line.

Start tracking a project already under way

Record where the work stands from the repository’s own files, with no questions asked first.

Record one table of many runs

A results.tsv in the top folder, one row a run, recorded with one command per arm.

Record a folder per run

Each run’s own folder, recorded from what its config says.

Check a summary's claims against the runs

Turn each claim in an agent’s summary into the criterion it states, and let rb read it.

Declare the criterion before the runs

Declare what counts and freeze it, so the finding says it came first.

Compare against a published baseline

Cite the paper’s number and settings, and get reproduced or not reproduced.

Get an interval, not a single number

Run seeds until the criterion has the interval it needs.

Read a rule over seeds

A count, a best of N and a relative change, each read its own way.

Share the record, and rerun it

A page your advisor reads, and a bundle their agent clones and reruns.

Rerun a run from its receipt

The command and the commit from the receipt, and a repeat that checks the run.

rb with Claude Code, Codex and Cursor

One record, whichever agent writes to it.

About the output on these pages

Every output block is real. For each cookbook we made a small project in a folder of its own: a training or evaluation script that writes fixed numbers per seed, a few configs, and sometimes a plan or a paper’s table. Then we ran the commands its prompt asks for with rb 0.8.0, as the agent’s, in an agent session as Claude Code runs them, and the commands marked as yours in a plain terminal. Two things were changed after the runs: the folder’s path is shown as ~, and long outputs are cut where a line says so.

Ids such as run4k2xa9, hashes and times differ in your run.