Borrowing it
Nothing to install: this file belongs to ikamensh/kodo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ikamensh/kodo/dev/AGENTS.mdgit clone --depth 1 https://github.com/ikamensh/kodoWrote 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/ikamensh/kodo/agents-md)<a href="https://agentmods.dev/instructions/ikamensh/kodo/agents-md"><img src="https://agentmods.dev/badge/instructions/ikamensh/kodo/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.
<a href="https://agentmods.dev/instructions/ikamensh/kodo/agents-md"><img src="https://agentmods.dev/badge/instructions/ikamensh/kodo/agents-md.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.01641 | $0.01641 |
| Opus 5.5 | $0.00656 | $0.00656 |
| Sonnet 5.5 | $0.00328 | $0.00328 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
kodo 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rules for writing code in this repo
End-to-end test scenarios (mocked)
Primary user workflows and how to verify them with mocks (no API keys or real backends):
| Scenario | Script | What it verifies |
|---|---|---|
| Non-interactive run | scripts/smoke_test_cli.py |
CLI starts, mocked orchestrator runs one cycle, exits 0, JSON output |
| Full mocked run | scripts/run_cli_mocked.py |
Goal + team + launch flow, run_start/cycle_end/run_end emitted |
| Resume interrupted run | scripts/smoke_test_resume.py |
Creates incomplete run, kodo --resume finds it, passes correct ResumeState to orchestrator |
| Improve mode | scripts/smoke_test_improve.py |
Project type detection (app vs library), 7-stage improve plan, orchestrator receives plan |
| Interactive flow | scripts/smoke_test_interactive.py |
Goal input, team/orchestrator/model selection, refine skip, confirmation, launch |
| Improve full run | scripts/run_improve_mocked.py |
kodo --improve on buggy_project, plan built, cycle completes |
Log viewer (browser): python -m kodo.viewer <log.jsonl> or --serve --port 8080. scripts/verify_viewer_browser.py uses Playwright (optional dep) to verify embedded data, stats bar, timeline, expand button.
Report bug: kodo issue [RUN_ID] — resolves run like --resume (latest or by id), prompts for description (leave empty if crash obvious), packs run into run.tar.gz (log, config, goal, conversations), opens GitHub new-issue URL with run context pre-filled. User attaches the archive (GitHub rejects .jsonl). Tests: tests/cli/test_subcommands.py::TestCmdIssue.
Steering input (kodo/cli/_interactive.py): deliberately no persistent prompt line or status bar — any always-visible UI needs a renderer that redraws around every output write, which desyncs and corrupts scrollback under tmux (issue #52). Instead a cbreak watcher opens a plain input() composer on first keypress; orchestrator output is buffered while composing. Don't reintroduce prompt_toolkit/TUI rendering here.
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 · 94 lines · 1,641 tokens per session scan A 2a96fb0a0a7b
kodo AGENTS.md is an instructions file published in the GitHub repository ikamensh/kodo (137 stars, last pushed 1mo ago), licensed MIT. It adds 1,641 tokens to every session, about $0.0066 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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.