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 agentmods add instructions/theillusionoflife/agentkaizen/agents-mdgit clone --depth 1 https://github.com/TheIllusionOfLife/AgentKaizenWrote 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/instructions/theillusionoflife/agentkaizen/agents-md)<a href="https://agentmods.dev/instructions/theillusionoflife/agentkaizen/agents-md"><img src="https://agentmods.dev/badge/instructions/theillusionoflife/agentkaizen/agents-md.svg" alt="Measured on agentmods" 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 | $0.01824 | $0.01824 |
| Opus 5 | $0.00912 | $0.00912 |
| Sonnet 5 | $0.00365 | $0.00365 |
| Haiku 4.5 | $0.00182 | $0.00182 |
Grade A, and why
AgentKaizen 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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Note for skill users: If you installed this skill via
npx skills add TheIllusionOfLife/optimize-coding-agent-skill, the commands in this file are for developing the AgentKaizen repository itself, not for using the skill. Skill users invoke the skill directly in their agent session — nouvorgit cloneneeded.
Purpose
This repository exists to improve CLI-based AI agent behavior with measurable feedback loops. The main product question is not just "can Codex solve a task?" but "which steering surface changed the behavior, and did it help enough to keep?"
Important steering surfaces in this repo include:
AGENTS.mdREADME.md- eval cases and variants
- external skill documents
- Codex CLI configuration and profiles
Required Environment
All workflows work without W&B. When Weave is not installed or unconfigured, AgentKaizen runs in local-only mode (traces to ~/.agentkaizen/traces.jsonl, local evaluation, regex-based PII redaction).
For W&B Weave integration (remote tracing and dashboards), set:
WANDB_API_KEYWANDB_PROJECT
WANDB_ENTITY is also needed for Weave, but it may come from WANDB_ENTITY, .env.local, or the logged-in W&B account if not passed explicitly.
Do not hardcode personal W&B entity or project values in code, docs, examples, or tests.
Useful optional environment variables:
WANDB_BASE_URLfor custom or self-hosted W&B deploymentsWEAVE_PARALLELISMfor tuning eval concurrencyWEAVE_PRINT_CALL_LINK=falsefor CI or other non-interactive runsWEAVE_LOG_LEVELwhen debugging Weave integration behaviorWEAVE_DISABLED=truefor local runs where tracing should be bypassed
Commands You Should Use (Repo Development)
These commands are for developing the AgentKaizen repository. Skill users do not need to run any of these.
Use uv for all Python workflows.
Common commands:
uv sync --group devuv run agentkaizen run --prompt "Say only: ok"uv run agentkaizen run --agent claude-code --prompt "Say only: ok"uv run agentkaizen session sync --onceuv run agentkaizen session sync --agent claude-code --onceuv run agentkaizen session score --trace-file path/to/interactive-trace.jsonuv run agentkaizen eval casegen --limit 20 --output evals/cases.generated.jsonluv run agentkaizen eval --cases evals/cases --variant-file evals/variants/<file>.jsonuv run --group dev pytestuv run --group dev ruff check .uv run --group dev ruff format --check .
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.
- 4d ago First seen · 123 lines · 1,824 tokens per session scan A a4b225453d0b
AgentKaizen AGENTS.md is an instructions file published in the GitHub repository TheIllusionOfLife/AgentKaizen (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 1,824 tokens to every session, about $0.0091 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.