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/kcsinclair/kaos-control/agents-mdgit clone --depth 1 https://github.com/kcsinclair/kaos-controlWhat 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.02324 | $0.02324 |
| Opus 5 | $0.01162 | $0.01162 |
| Sonnet 5 | $0.00465 | $0.00465 |
| Haiku 4.5 | $0.00232 | $0.00232 |
Grade A, and why
kaos-control 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 135 lines · 2,324 tokens per session scan A 1b9f4ad73cca
kaos-control AGENTS.md is an instructions file published in the GitHub repository kcsinclair/kaos-control (13 stars, last pushed 6d ago), with no licence file. It adds 2,324 tokens to every session, about $0.0116 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-30.
Other instructions, from other repositories
mantis AGENTS.md
Instructions for google/mantis, covering agent rules, before committing, verbatim blocks, reference files and extraction criteria.
debroid AGENTS.md
Instructions for PatilShreyas/debroid, covering ai agent contributor guide 🤖, 🎯 intention & motivation, 🏗️ architecture & layers, 1. the core layer (jdi & adb orchestration) and 2. the cli layer (daemon & client).
isomux AGENTS.md
Instructions for nmamano/isomux, covering isomux, how to develop, formatting and linting, key decisions (do not revisit) and project layout.
agents CLAUDE.md
Instructions for eloylp/agents, covering claude.md, project overview, directory structure, config model and build & run.
open-bridge AGENTS.md
Instructions for bks-lab/open-bridge, covering the bridge — agent instructions, required reading, session start detection (automatic), theme and agents.
free-ai-gateway AGENTS.md
Instructions for zaber-dev/free-ai-gateway, covering 🤖 free-ai gateway - agentic development guidelines, 🏛️ monorepo architecture & package boundaries, 🛑 strict architectural rules for agents, 💻 essential developer commands and build all packages across monorepo.