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/isaacsight/kernel/agents-mdgit clone --depth 1 https://github.com/isaacsight/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/isaacsight/kernel/agents-md)<a href="https://agentmods.dev/instructions/isaacsight/kernel/agents-md"><img src="https://agentmods.dev/badge/instructions/isaacsight/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.00897 | $0.00897 |
| Opus 5 | $0.00449 | $0.00449 |
| Sonnet 5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
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 today.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — kernel.chat operating contract for Codex
Codex auto-loads this file. It is the operating contract, not the full reference. Read the linked docs before design work. The canonical project reference is
KERNEL.md.
What this is (30 seconds)
Two surfaces, one publication. (1) kbot — an open-source terminal AI agent. (2) kernel.chat — an editorial magazine. You will almost always be working on the magazine: interactive issues, spreads, and standalone artifacts. The room is a magazine; speak like one.
Read before you design
The detailed design, interaction, and verification law lives outside this file. Before any design or layout task, read:
.agents/AGENTS.md— full design / interaction / verification lawKERNEL.md— project shape, directory map, ship flowdocs/design-language.md— visual grammardocs/interaction-language.md— motion + calmness law
Non-negotiables (these override convenience)
- Magazine vocabulary in all user-visible copy: issue, feature, spread, folio, monument, colophon, dateline, postmark — never dashboard, panel, card, widget, modal. Never name the visual homage ("POPEYE") on the site.
- No emojis in code or user-visible copy. The single system asterisk
★is the only exception. - No JS animation runtimes (Framer Motion, motion.dev, Lottie) on editorial
surfaces. Page/editorial motion is CSS-only. Script motion is allowed only
inside a framed mechanism (
plate/bore) and must collapse underprefers-reduced-motion. - Never touch secrets. Do not read, edit, print, or commit
.env,*.key,*.pem, orsupabase/config.tomlsecrets. Never hardcode keys or tokens. - Never push to
main. See workflow below —mainis the live publisher.
How you work (full-auto, one hard stop)
You work autonomously. Branch, edit, verify, commit, push the branch, open a PR
— all without asking. You stop at exactly one line: merging or pushing to
main. That is a human decision because it deploys.
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.
- today First seen · 82 lines · 897 tokens per session scan A 1b31d3867baf
kernel AGENTS.md is an instructions file published in the GitHub repository isaacsight/kernel (16 stars, last pushed 5d ago), licensed MIT. It adds 897 tokens to every session, about $0.0045 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-09-03.
Other instructions, from other repositories
maidan CLAUDE.md
Instructions for david-engelmann/maidan, covering agent guide, 30-second orientation, read order, the cluster model in one paragraph and pr workflow (the short version).
prime-silo CLAUDE.md
Instructions for binary16labs/prime-silo, covering prime-silo agent navigation, current status (as of 2026-07-16), architecture in one sentence, what agents need to know and 1. agent authority (strict boundaries).
prime-silo AGENTS.md
Instructions for binary16labs/prime-silo, covering agents, documentation first, agents file index, programming guide and top-level structure.
maidan AGENTS.md
Instructions for david-engelmann/maidan: If you are connecting to a Maidan server (not hacking on this Rust repo), start here.
YodMCP AGENTS.md
AGENTS.md instructions for ANAMIZED/YodMCP, covering agents.md — working on yodmcp and new repos.
Cotal AGENTS.md
AGENTS.md instructions for Cotal-AI/Cotal, covering agents.md, what this is, read these first, commands and repository map.