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 0xagentkitchen/kitchenloop --skill kitchenloop-ideategit clone --depth 1 https://github.com/0xagentkitchen/kitchenloopWrote 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/0xagentkitchen/kitchenloop/kitchenloop-ideate)<a href="https://agentmods.dev/skills/0xagentkitchen/kitchenloop/kitchenloop-ideate"><img src="https://agentmods.dev/badge/skills/0xagentkitchen/kitchenloop/kitchenloop-ideate/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/0xagentkitchen/kitchenloop/kitchenloop-ideate"><img src="https://agentmods.dev/badge/skills/0xagentkitchen/kitchenloop/kitchenloop-ideate.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.00000 | $0.01949 |
| Opus 5.5 | $0.00000 | $0.00780 |
| Sonnet 5.5 | $0.00000 | $0.00390 |
| Haiku 4.5 | $0.00000 | $0.00195 |
Grade A, and why
kitchenloop-ideate 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 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.
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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KitchenLoop: Ideate
Phase 1 -- Brainstorm a usage scenario, implement it, test it, write an experience report.
Triggers
kitchenloop ideateloop ideatebrainstorm scenario
Overview
The Ideate phase is where the loop generates new work. You act as a synthetic user of the project: pick a realistic scenario, try to implement it using the project's public API and tooling, document what works and what doesn't, and produce a structured experience report that the Triage phase will later convert into tickets.
Scenario Tiers
T1 -- Foundation (single feature, happy path)
- Exercise ONE feature from the
spec.dimensionssection ofkitchenloop.yaml - Follow the documented happy path exactly
- Goal: verify basics still work, catch regressions early
- Example: "Use the auth module to register a user and log in"
T2 -- Composition (combine features)
- Exercise TWO OR MORE features together in a realistic workflow
- Goal: catch integration seams, data-flow mismatches, missing error handling
- Example: "Register a user, create a payment, then generate a report"
T3 -- Frontier (push boundaries)
- Attempt something the project does not explicitly support yet
- Goal: discover missing capabilities, poor error messages, edge cases
- Example: "Use the reports API with a date range that spans a timezone change"
Tier selection rule: If the last 3 iterations were all T1, escalate to T2. If T2 scenarios have high pass rates (>90%), try T3. If T3 keeps failing on the same root cause, file a blocker ticket and drop back to T2.
Procedure
Step 1: Read Context
- Load
kitchenloop.yaml-- readspec.dimensions,spec.blocked,paths, andverification. - Read loop state at the path specified by
paths.loop_state:- What iteration number is this?
- What scenarios were tried in recent iterations?
- What tiers have been used recently?
- Read the spec docs listed in
spec.docsto understand project capabilities. - If
paths.patternsexists, read it for known codebase patterns and pitfalls.
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 · 224 lines · 0 tokens per session scan A 0dd2a91d920d
kitchenloop-ideate is a skill published in the GitHub repository 0xagentkitchen/kitchenloop (23 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,949 tokens. 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-30.
kitchenloop-ideate compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| kitchenloop-ideate0xagentkitchen/kitchenloop | Skill | 23 | 7mo ago | MIT | A | 0 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |