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/anthony-chaudhary/dos-kernel/agents-mdgit clone --depth 1 https://github.com/anthony-chaudhary/dos-kernelWrote 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/anthony-chaudhary/dos-kernel/agents-md)<a href="https://agentmods.dev/instructions/anthony-chaudhary/dos-kernel/agents-md"><img src="https://agentmods.dev/badge/instructions/anthony-chaudhary/dos-kernel/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.04444 | $0.04444 |
| Opus 5 | $0.02222 | $0.02222 |
| Sonnet 5 | $0.00889 | $0.00889 |
| Haiku 4.5 | $0.00444 | $0.00444 |
Grade A, and why
dos-kernel 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — orientation for an AI agent working in this repo
You are an AI agent reading this repo to understand it or change it. This file is your front door: what DOS is in three lines, how to build and check your work, the short list of files actually worth reading, and the rules the kernel enforces on its own contributors. It is deliberately short and navigational — the detail lives behind the links.
Fitting, given what DOS is: the kernel exists to not believe an agent's self-report. So don't take this file on faith either — every claim here is one you can check with a
doscommand or agitread, and where that's the point, the command is shown. (Human-oriented? Read README.md instead; it is the same story written for a person browsing GitHub.)
What DOS is (the 30-second version)
DOS is a small, deterministic kernel that referees a fleet of AI agents working on a shared git repo. Every agent narrates — "I shipped it," "tests pass," "still making progress." DOS treats all of that as a claim, not a fact, and hands back a verdict read from ground truth the agent could not have authored: git history, the file tree, a clock, an environment's own state.
verify— did(plan, phase)actually ship? (from git ancestry, never the agent's word)arbitrate— may this agent take this lane, or does it collide with one already running?liveness— is the run ADVANCING, or just SPINNING / STALLED?refuse— say no with a reason a machine can act on.
Nothing here is coding-specific: a repo declares its own rules (lanes, paths,
ship-stamp grammar) as data in dos.toml; the kernel supplies only the
machinery. Reach it from the dos CLI, an MCP server, or import dos.
Run it yourself first — the 60-second proof
Before reading anything, watch the core idea happen:
pip install -e . # editable install from this clone (PyYAML is the only runtime dep)
dos quickstart # scaffolds a throwaway repo, commits, then:
# SHIPPED AUTH AUTH1 … (via grep-subject) exit 0
# NOT_SHIPPED AUTH AUTH2 … (via none) exit 1
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 · 232 lines · 4,444 tokens per session scan A f4af44e93093
dos-kernel AGENTS.md is an instructions file published in the GitHub repository anthony-chaudhary/dos-kernel (19 stars, last pushed 10d ago), licensed MIT. It adds 4,444 tokens to every session, about $0.0222 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
takt AGENTS.md
AGENTS.md instructions for nrslib/takt, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
PuPu CLAUDE.md
Instructions for haoxiang-xu/PuPu, covering gitnexus — code intelligence, always do, never do, resources and cli.
rondoflow CLAUDE.md
Claude Code instructions for rondoflow/rondoflow, covering rondoflow, project overview, tech stack, development and setup.
claude-org-ja CLAUDE.md
Instructions for suisya-systems/claude-org-ja, covering secretary, 事実は出典付きで書く(citation-or-abstain), 起動時, コミュニケーション and 輸送層(transport)両系 — 既定 renga / opt-in broker.
teamctl CLAUDE.md
Instructions for Alireza29675/teamctl, covering claude.md, what this repo is, stack and entry points, cross-cutting rules and how agents behave in this repo.
Polaris AGENTS.md
Instructions for sponge-b0b/Polaris, covering agents.md, purpose and authority, domain vocabulary, coding conduct and secrets.