What is kitchenloop AGENTS.md?

Development instructions for KitchenLoop, an automated improvement process for a codebase. It moves work through planning, idea review, implementation, cleanup, and regression testing, then can open a pull request.

Use it when configuring or modifying KitchenLoop's shell orchestrator, prompts, libraries, worktree handling, testing gates, or automated improvement phases.

It documents the loop's phases, shared terms, files, and configuration so contributors can understand how automated changes are proposed and checked. A pull request is a reviewable set of code changes.

How 0xagentkitchen/kitchenloop configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to 0xagentkitchen/kitchenloop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/0xagentkitchen/kitchenloop/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/0xagentkitchen/kitchenloop

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/0xagentkitchen/kitchenloop/agents-md/github.svg)](https://agentmods.dev/instructions/0xagentkitchen/kitchenloop/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/0xagentkitchen/kitchenloop/agents-md"><img src="https://agentmods.dev/badge/instructions/0xagentkitchen/kitchenloop/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/0xagentkitchen/kitchenloop/agents-md"><img src="https://agentmods.dev/badge/instructions/0xagentkitchen/kitchenloop/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,113 This file is loaded in full into every session.

When invoked 1,113 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01113	$0.01113
Opus 5.5	$0.00445	$0.00445
Sonnet 5.5	$0.00223	$0.00223
Haiku 4.5	$0.00111	$0.00111

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

Security

Grade A, and why

kitchenloop AGENTS.md 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.

AGENTS.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

KitchenLoop

Autonomous improvement loop for any codebase, powered by Claude Code. Runs six phases in sequence: Backlog → Ideate → Triage → Execute → Polish → Regress. Each iteration picks work, implements it, tests it adversarially, and opens a PR — all without human intervention.

Key Concepts

Spec surface — the matrix of features x platforms x actions your product claims to support
Unbeatable tests — end-to-end verification against ground truth that the code author cannot fake
UAT gate — post-implementation adversarial testing by a fresh agent with zero context
Drain mode — auto-triggered when PR backpressure exceeds a configured threshold
Discussion Manager — multi-AI deliberation with anti-sycophancy safeguards

Architecture

scripts/kitchenloop/
  kitchenloop.sh          # Main orchestrator (~2000 lines bash). Runs phases via Claude Code subprocess.
  prompts/                # Phase prompts: ideate.md, execute.md, triage.md, polish.md, regress.md, backlog.md
                          # Uses template variables: {{REPO_ROOT}}, {{WORKTREE}}, {{BRANCH}}, etc.
  lib/                    # Internal helpers for the orchestrator

lib/
  config.sh               # yq-based config loader. Reads kitchenloop.yaml.
  paths.sh                # Artifact path resolver. All paths go through here.
  tickets.sh              # Ticket adapter (GitHub Issues / Linear).

scripts/ai-discussion/
  discuss.py              # Multi-AI discussion orchestrator (Python 3.10+). Anti-sycophancy safeguards.

scripts/pr-manager/       # Automated PR lifecycle: create, label, merge, drain.

skills/                   # Source skill definitions. Copied to .claude/skills/ by the init script.
                          # Skills in .claude/skills/ are auto-discovered by Claude Code. Each has a SKILL.md.
                          # The prompts in scripts/kitchenloop/prompts/ are lightweight versions;
                          # the full skills have more detail.
templates/                # Template files for new project scaffolding.
examples/                 # Example configs (Python CLI, Web API).
docs/howto.md             # Operator manual for running KitchenLoop.
kitchenloop.example.yaml  # Reference configuration with all available options.

Read the full file on GitHub · 108 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.

2mo ago First seen · 108 lines · 1,113 tokens per session scan A 32496e0ba157

Subscribe to this mod's changes

kitchenloop AGENTS.md is an instructions file published in the GitHub repository 0xagentkitchen/kitchenloop (23 stars, last pushed 7mo ago), licensed MIT. It adds 1,113 tokens to every session, about $0.0045 per session on Opus 5.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-30.

Building agents Planning

kitchenloop AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
kitchenloop AGENTS.md0xagentkitchen/kitchenloop	Instructions file	23	7mo ago	MIT	A	1,113	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

kitchenloop: Instructions file for Codex