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/jordanhubbard/agentos/agents-mdgit clone --depth 1 https://github.com/jordanhubbard/agentosWrote 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/jordanhubbard/agentos/agents-md)<a href="https://agentmods.dev/instructions/jordanhubbard/agentos/agents-md"><img src="https://agentmods.dev/badge/instructions/jordanhubbard/agentos/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.01055 | $0.01055 |
| Opus 5 | $0.00528 | $0.00528 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
agentos 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentOS — Agent Development Guidelines
Mandatory. Violations are rejected. Full constitution: CLAUDE.md. TCB: docs/TCB.md. Plan: PLAN.md.
What This Project Is
agentOS is a seL4 OS that owns devices in user mode and hosts Linux and FreeBSD as virtio guests. QEMU pretends to be a board. The real target is bare metal.
There is no POSIX userland. There is no "ring 1–5". seL4 is EL2. Our PDs are EL0. Guest kernels are EL1 and are hostile.
If you do not understand seL4 IPC and sDDF queues, read the seL4 Microkit
manual and libvmm/dep/sddf/docs/network/network.md before writing I/O code.
The Rules
1. TCB first
Only PDs in docs/TCB.md may own a device frame or IRQ. Museum PDs listed
there must not be extended.
2. No human UI here
No HTML/JS served by a process in this repo. Skill helpers may print HTML for LLM agents.
3. On-target: C / Rust / ASM. Host skills: Python.
Python in skills/ and tools/ only. Never in kernel/ live PDs.
4. Guests speak virtio that we emulate
Use libvmm virtio device backends (virtio_mmio_net_init, blk, console).
Do not map QEMU virtio-mmio into the guest. Host virtio is for the driver PD.
5. Contracts before callers
Queue layout in platform/include/platform/. IPC in
kernel/agentos-root-task/include/contracts/. Tests must assert outputs.
6. Make is the interface
If a Makefile rule exists, use it (make build, make test, make gate).
How to Add I/O (the only new "PD" path that matters)
- Driver PD owns the physical (or QEMU-stand-in) device.
- Virtualizer PD muxes sDDF queues to N clients.
- VMM calls libvmm
virtio_mmio_*_initat a guest IPA that faults. - Guest DTB describes that emulated device, not the host MMIO.
- Host test for the pump/mux; QEMU test that the guest sees the device.
Do not add MSG_*_OPEN opcode tables as a substitute for queues.
How to Add a Skill
skills/<block>/SKILL.md # small: invariants, forbidden moves, helper
skills/<block>/scripts/*.py # compute; print HTML to stdout
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 Changed · -243 lines · -2,579 tokens per session be1ba51daba1
- 4d ago First seen · 370 lines · 3,634 tokens per session scan A bbfc0eae87fd
agentos AGENTS.md is an instructions file published in the GitHub repository jordanhubbard/agentos (25 stars, last pushed today), licensed BSD-2-Clause. It adds 1,055 tokens to every session, about $0.0053 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
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.