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 skills add 2389-research/test-kitchen --skill omakase-offgit 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/omakase-off)<a href="https://agentmods.dev/skills/2389-research/test-kitchen/omakase-off"><img src="https://agentmods.dev/badge/skills/2389-research/test-kitchen/omakase-off/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/skills/2389-research/test-kitchen/omakase-off"><img src="https://agentmods.dev/badge/skills/2389-research/test-kitchen/omakase-off.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.00079 | $0.01120 |
| Opus 5 | $0.00039 | $0.00560 |
| Sonnet 5 | $0.00016 | $0.00224 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
omakase-off 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 9d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Omakase-Off
Chef's choice exploration - when you're not sure WHAT to build, explore different approaches in parallel.
Part of Test Kitchen Development:
omakase-off- Chef's choice exploration (different approaches/plans)cookoff- Same recipe, multiple cooks compete (same plan, multiple implementations)
Core principle: Let indecision emerge naturally during brainstorming, then implement multiple approaches in parallel to let real code + tests determine the best solution.
Three Triggers
Trigger 1: BEFORE Brainstorming
When: "I want to build...", "Create a...", "Implement...", "Add a feature..."
Present:
Before we brainstorm the details, would you like to:
1. Brainstorm together - We'll explore requirements and design step by step
2. Omakase (chef's choice) - I'll generate 3-5 best approaches, implement them
in parallel, and let tests pick the winner
Trigger 2: DURING Brainstorming (Indecision Detection)
Detection signals:
- 2+ uncertain responses in a row on architectural decisions
- Phrases: "not sure", "don't know", "either works", "you pick", "no preference"
When detected:
You seem flexible on the approach. Would you like to:
1. I'll pick what seems best and continue brainstorming
2. Explore multiple approaches in parallel (omakase-off)
Trigger 3: Explicitly Requested
- "try both approaches", "explore both", "omakase"
- "implement both variants", "let's see which is better"
Workflow Overview
| Phase | Description |
|---|---|
| 0. Entry | Present brainstorm vs omakase choice |
| 1. Brainstorm | Passive slot detection during design |
| 1.5. Decision | If slots detected, offer parallel exploration |
| 2. Plan | Generate implementation plan per variant |
| 3. Implement | Dispatch ALL agents in SINGLE message |
| 4. Evaluate | Scenario tests → fresh-eyes → judge survivors |
| 5. Complete | Finish winner, cleanup losers |
See references/detailed-workflow.md for full phase details.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 140 lines · 79 tokens per session scan A 09fc73aba212
omakase-off is a skill published in the GitHub repository 2389-research/test-kitchen (4 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 1,120 once invoked, about $0.0004 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).
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.
comparison-post-writer
Write "X vs Y" comparison blog posts that help readers choose between two competing products. Triggers on: "write a comparison post", "X vs Y blog post", "compare [product A] and [product B]", "which is better [A] or [B]", "head to head comparison", "[product] vs [product] article", "comparison review", "write a…