kitchenloop-ideate

kitchenloop-ideate is a skill for Claude Code, Codex from 0xagentkitchen/kitchenloop. It costs 0 tokens per session (1,949 once invoked), scanned A, original, MIT.

The idea-generation stage of KitchenLoop, an automated software-development cycle. It acts like a project user, tries realistic tasks through the project's public tools, and records what works or fails.

In plain words
What is it for?
It helps test simple features, combined workflows, and boundary cases, then creates an experience report that can be turned into work items.
Why use it?
It exposes missing features, broken workflows, and integration problems by testing the project as someone would actually use it.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit It helps test simple features, combined workflows, and boundary cases, then creates an experience report that can be turned into work items.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/0xagentkitchen/kitchenloop/kitchenloop-ideate
Install

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.

Any agent
npx skills add 0xagentkitchen/kitchenloop --skill kitchenloop-ideate
Clone the repo
git clone --depth 1 https://github.com/0xagentkitchen/kitchenloop

Made for: Claude Code, Codex.

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 kitchenloop-ideate

README.md
[![agentmods](https://agentmods.dev/badge/skills/0xagentkitchen/kitchenloop/kitchenloop-ideate/github.svg)](https://agentmods.dev/skills/0xagentkitchen/kitchenloop/kitchenloop-ideate)
Your own site
<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.

agentmods 80×15 button for kitchenloop-ideate

Your own site · 80×15
<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>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,949 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.01949
Opus 5.5 $0.00000 $0.00780
Sonnet 5.5 $0.00000 $0.00390
Haiku 4.5 $0.00000 $0.00195

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

Security

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.

skills/kitchenloop-ideate/SKILL.md · 224 lines

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 ideate
  • loop ideate
  • brainstorm 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.dimensions section of kitchenloop.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

  1. Load kitchenloop.yaml -- read spec.dimensions, spec.blocked, paths, and verification.
  2. 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?
  3. Read the spec docs listed in spec.docs to understand project capabilities.
  4. If paths.patterns exists, read it for known codebase patterns and pitfalls.

Read the full file on GitHub · 224 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 · 224 lines · 0 tokens per session scan A 0dd2a91d920d

Subscribe to this mod's changes

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.

Related

kitchenloop-ideate compared with skills from other repositories

kitchenloop-ideate next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
kitchenloop-ideate0xagentkitchen/kitchenloopSkill237mo agoMITA0Claude Code, Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code