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/smartcomputer-ai/agent-os/agents-mdgit clone --depth 1 https://github.com/smartcomputer-ai/agent-osWhat 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.02399 | $0.02399 |
| Opus 5 | $0.01200 | $0.01200 |
| Sonnet 5 | $0.00480 | $0.00480 |
| Haiku 4.5 | $0.00240 | $0.00240 |
Grade A, and why
agent-os 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents
This file provides guidance to coding agents when working with code in this repository.
What This Is
AgentOS is a deterministic, event-sourced computing substrate for AI agents.
AIR (Agent Intermediate Representation) is the typed control-plane IR governing schemas, modules, effects, secrets, and manifests.
Reading the Specs (index)
- spec/01-overview.md — Core concepts and mental model.
- spec/02-architecture.md — Runtime components, storage layout, governance phases.
- spec/03-air.md — CRITICAL AIR v1 spec (post-plan active model).
- spec/04-workflows.md — Workflow module semantics and orchestration patterns.
- spec/05-effects.md — Effects, async execution, durable open work, and continuation admission.
- spec/06-backends.md — Backend contracts, SQLite/Kafka journals, local/object-store CAS, and recovery.
Future protocol notes:
- spec/20-gc.md — GC/reachability contract draft; deletion GC is not implemented yet.
Reference shelves:
- spec/schemas/ (JSON Schemas)
- spec/defs/ (built-ins: Timer/Blob/HTTP/LLM/Workspace/Introspect plus SDK support schemas)
Core Architecture (TL;DR)
World: Single-threaded deterministic kernel state. Replay checkpoint/snapshot + journal frames + receipts = identical state.
Workspaces: Versioned tree registry (sys/Workspace@1). Tree ops (workspace.*) are internal effects used by aos ws plus aos push/aos pull.
Active layers:
- Workflow modules (WASM,
module_kind: workflow): deterministic state machines on workflow ABI; own orchestration/state transitions. - Pure modules (
module_kind: pure): side-effect-free compute helpers. - Kernel (
aos-kernel): synchronous authoritative world execution, governance, manifests, effect authorization, snapshots, replay, and open-work state. - Unified node (
aos-node): owns hot worlds, serializes per-world execution, stages completed slices, durably flushes journal frames, serves hot control reads, and publishes opened async effects only after durable append. - Executors/Adapters: async edge execution for external work; stream frames and receipts re-enter only as world input through owner admission.
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 · 161 lines · 2,399 tokens per session scan A 95af21ecc61b
agent-os AGENTS.md is an instructions file published in the GitHub repository smartcomputer-ai/agent-os (210 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 2,399 tokens to every session, about $0.0120 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
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.
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).
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.