What is the-kitchen AGENTS.md?

A project guide for coding agents working on a software repository. It defines the product goals, architecture expectations, testing approach, and rules for keeping the guide current.

Use it to guide repository setup, implementation, testing, architecture decisions, and updates to the project’s operating rules.

It gives an automated coding agent a shared set of instructions before it changes code, including TDD—writing a failing test, making it pass, and then cleaning up the code.

How jozef-barton/the-kitchen configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to jozef-barton/the-kitchen. 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/jozef-barton/the-kitchen/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/jozef-barton/the-kitchen

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/jozef-barton/the-kitchen/agents-md/github.svg)](https://agentmods.dev/instructions/jozef-barton/the-kitchen/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/jozef-barton/the-kitchen/agents-md"><img src="https://agentmods.dev/badge/instructions/jozef-barton/the-kitchen/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/jozef-barton/the-kitchen/agents-md"><img src="https://agentmods.dev/badge/instructions/jozef-barton/the-kitchen/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 4,284 This file is loaded in full into every session.

When invoked 4,284 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.04284	$0.04284
Opus 5.5	$0.01714	$0.01714
Sonnet 5.5	$0.00857	$0.00857
Haiku 4.5	$0.00428	$0.00428

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

Security

Grade A, and why

the-kitchen 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 · 320 lines

How it starts

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

AGENTS.md

This repository is intended to be completed autonomously by a coding agent such as Codex. Treat this file as the persistent execution charter and product/architecture specification. Update it whenever architecture decisions, constraints, or risks materially change.

Agent operating contract

Read this file fully before changing code.
Keep this file current. When an architectural or design decision changes, revise the affected section — do not maintain a dated completion ledger here.
Work autonomously in small, verifiable increments until acceptance criteria are met.
Do not stop at scaffolding. Leave the repository with a working vertical slice.
Follow TDD where practical:
- write a failing test
- implement the minimum code
- make the test pass
- refactor safely
Never disable tests, typechecks, lint rules, or security checks to move faster.
The runtime architecture is browser-first. Do not restore Electron IPC or renderer assumptions as the primary path.
Prefer structured schemas, explicit persistence models, and explicit failure states.
Preserve a minimal, modern, internal-scrollable UI.
If a better implementation detail is discovered, update this file before or alongside the code.
Before declaring a phase complete, run the relevant verification command.
When making changes, validate the local command path used by GitHub Actions before handoff; today that means running pnpm ci:full (lint, typecheck, unit tests, security). End-to-end Playwright runs are not part of CI today; run them separately with pnpm exec playwright test when a change affects the e2e surface.

Product vision

Build a local-first Hermes frontend with:

a browser-based chat interface with streaming markdown
real Hermes profile and session browsing
persisted local Spaces attached to sessions, with synchronized markdown/table/card content representations, extensible content-first tabs, and combined session+space workspaces
jobs / cron visibility
tool listing and reviewed tool execution history
explicit disconnected, degraded, error, and empty states
clean restart-safe persistence for hundreds of chats and thousands of messages

Read the full file on GitHub · 320 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 · 320 lines · 4,284 tokens per session scan A b4dc19bb65c6

Subscribe to this mod's changes

the-kitchen AGENTS.md is an instructions file published in the GitHub repository jozef-barton/the-kitchen (58 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 4,284 tokens to every session, about $0.0171 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.

the-kitchen AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
the-kitchen AGENTS.mdjozef-barton/the-kitchen	Instructions file	58	4mo ago	Apache-2.0	A	4,284	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	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	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

the-kitchen: Instructions file for Codex