Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/2389-research/test-kitchen/cookoffnpx skills add 2389-research/test-kitchen --skill cookoffgit clone --depth 1 https://github.com/2389-research/test-kitchenWrote 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/skills/2389-research/test-kitchen/cookoff)<a href="https://agentmods.dev/skills/2389-research/test-kitchen/cookoff"><img src="https://agentmods.dev/badge/skills/2389-research/test-kitchen/cookoff.svg" alt="Measured on agentmods" 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.00068 | $0.03384 |
| Opus 5 | $0.00034 | $0.01692 |
| Sonnet 5 | $0.00014 | $0.00677 |
| Haiku 4.5 | $0.00007 | $0.00338 |
Grade A, and why
cookoff 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 6d 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cookoff
Same design, multiple cooks compete. Each implementation team creates their own plan from the shared design, then implements it. Natural variation emerges from independent planning decisions.
Part of Test Kitchen Development:
omakase-off- Chef's choice exploration (different approaches/designs)cookoff- Same design, multiple cooks compete (each creates own plan + implements)
Key insight: Don't share a pre-made implementation plan. Each agent generates their own plan from the design doc, ensuring genuine variation.
Directory Structure
docs/plans/<feature>/
design.md # Input: from brainstorming
cookoff/
impl-1/
plan.md # Agent 1's implementation plan
impl-2/
plan.md # Agent 2's implementation plan
impl-3/
plan.md # Agent 3's implementation plan
result.md # Cookoff results and winner
Skill Dependencies
| Reference | Primary (if installed) | Fallback |
|---|---|---|
writing-plans |
superpowers:writing-plans |
Each agent writes their own implementation plan |
executing-plans |
superpowers:executing-plans |
Execute plan tasks sequentially with verification |
parallel-agents |
superpowers:dispatching-parallel-agents |
Dispatch multiple Task tools in single message |
git-worktrees |
superpowers:using-git-worktrees |
git worktree add .worktrees/<name> -b <branch> |
tdd |
superpowers:test-driven-development |
RED-GREEN-REFACTOR cycle |
verification |
superpowers:verification-before-completion |
Run command, read output, THEN claim status |
fresh-eyes |
fresh-eyes-review:skills (2389) |
2-5 min review for security, logic, edge cases |
judge |
test-kitchen:judge |
Scoring framework with checklists (MUST invoke at Phase 4) |
code-review |
superpowers:requesting-code-review |
Dispatch code-reviewer subagent |
scenario-testing |
scenario-testing:skills (2389) |
.scratch/ E2E scripts, real dependencies |
finish-branch |
superpowers:finishing-a-development-branch |
Verify tests, present options, cleanup |
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.
- 6d ago First seen · 396 lines · 68 tokens per session scan A 55bcad4b3dba
cookoff is a skill published in the GitHub repository 2389-research/test-kitchen (4 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 3,384 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
sketch
Throwaway HTML mockups: 2-3 design variants to compare.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows.
ai-loop
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
cross-wave-delta-analysis
Compare recon waves to find NEW, REGRESSED, PERSISTENT findings.