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/claude-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/claude-md)<a href="https://agentmods.dev/instructions/jordanhubbard/agentos/claude-md"><img src="https://agentmods.dev/badge/instructions/jordanhubbard/agentos/claude-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.1 | $0.01629 | $0.01629 |
| Opus 5 | $0.00814 | $0.00814 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
agentos CLAUDE.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 yesterday.
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentOS — Project Constitution for AI Agents
This document is binding. Read docs/TCB.md first. Do not make exceptions.
What agentOS Is
agentOS is a bootable, capability-secured operating system on the seL4 microkernel. It is the I/O and isolation platform for:
- Linux and FreeBSD as guests (in-tree virtio drivers only)
- Native purpose-driven PDs / agents that never run a legacy OS
QEMU is a hardware emulator for fast prototyping. The same driver PDs that own QEMU virtio-mmio as a stand-in NIC/disk will own real devices on bare metal.
agentOS is not a thin hypervisor slave to QEMU. It is not a web app. It is not a dashboard. It boots on bare metal.
Trusted Computing Base
See docs/TCB.md. Short form:
- seL4 is the only kernel-mode code. Never modify it.
- Root task distributes untyped memory, CSpace, VSpace, and initial caps. It does not enforce policy after spawn.
- Driver PDs own exactly one device class (frame + IRQ).
- Virtualizer PDs mux that class over sDDF-shaped shared-memory queues.
- VMM PDs run vCPUs/vGIC and emulate virtio for guests.
- Everyone else is a client or is quarantined (
docs/TCB.mdmuseum list).
There is no "Ring 1–5". Those numbers mixed Intel rings with ARM ELs with seL4 PDs and were wrong. Guest userspace runs in the guest VSpace.
Language Policy
On-target (PDs, libvmm backends, root task)
C, Rust, Assembly only. Freestanding. No Python runtime in a PD. No JavaScript. No Go, Zig, or other languages unless the project owner approves in writing.
Host composition (skills/, tools/)
Python is required for skill helpers and generators. Helpers must stay small: they compute (graphs, DTB/ELF/virtio inspection, topology) and print HTML (or another structured dump) for LLM agents. That HTML is not a product UI and must not be served by any PD.
CMake / Make orchestrate builds. Shell is CI glue and one-line wrappers.
WASM is a guest/agent binary format only. WASM runtime is C or Rust. WASM is not a NIC, disk, or UART.
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.
- yesterday Changed · -96 lines · -2,075 tokens per session 491b5355186a
- 5d ago First seen · 286 lines · 3,704 tokens per session scan A c3cbbdf08fe4
agentos CLAUDE.md is an instructions file published in the GitHub repository jordanhubbard/agentos (25 stars, last pushed today), licensed BSD-2-Clause. It adds 1,629 tokens to every session, about $0.0081 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
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.
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.
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.
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).