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/aterrylu/autonomos/agents-mdgit clone --depth 1 https://github.com/aterrylu/autonomOSWhat 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.01874 | $0.01874 |
| Opus 5 | $0.00937 | $0.00937 |
| Sonnet 5 | $0.00375 | $0.00375 |
| Haiku 4.5 | $0.00187 | $0.00187 |
Grade B, and why
autonomOS AGENTS.md scanned grade B with 2 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 3d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
Every spawned session gets `--settings` with inline hook entries for all 13 Claude Code events. Each hook runs `curl -d @- $AUTONOMOS_SERVER/api/hooks/$SESSION_ID`. The server processes events for agent status tracking ( Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
### Hook Relay (`--settings` inline curl) How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
autonomOS — Agent Development Guide
Start Here
- Read
README.md— project overview, monorepo structure - Read
docs/FEATURES.md— feature specifications and design intent - Read
docs/DECISIONS.md— all architectural decisions with context and rationale - Read
docs/ROADMAP.md— current priorities and what to work on - Read
docs/RESEARCH.md— research findings, competitor analysis, learnings
Project Vision
autonomOS is a mission control platform for autonomous agents — a terminal dashboard that spawns Claude Code sessions, tracks their status via hook telemetry, and enables multi-agent coordination through a messaging gateway.
Current state: Terminal dashboard + session management + hook relay + multi-agent gateway + MCP tools. The orchestrator/projects/workspaces model described below is the long-term vision, not yet implemented.
Core concepts (future):
- Orchestrator — PM agent, the main interface. Understands project goals, delegates to workspace agents, tracks progress.
- Projects — Logical goals with roadmaps. Can span multiple workspaces. Multiple projects per workspace.
- Workspaces — Physical repositories, auto-discovered. Each has active agent sessions.
Two paths that share a common core:
- Dev Path — control plane for agent tools (Claude Code, etc.)
- Robot Path — persistent agent platform for robotics (aspirational, future)
Monorepo Structure
autonomOS/
├── packages/
│ ├── dashboard/ # Web UI — observability & control
│ │ └── src/layout/ # Binary tree split-pane system
│ ├── server/ # Hono + node-pty — API, WebSocket, PTY management
│ │ ├── src/gateway/ # URI-based message router + platform adapters
│ │ ├── src/channel-server/ # Standalone MCP subprocess (server:autonomos)
│ │ └── src/mcp/ # Shared MCP tool definitions (used by both servers)
│ └── core/ # Shared agent abstractions & types
├── docs/
│ ├── DECISIONS.md # Architectural Decision Records (append-only)
│ ├── FEATURES.md # Feature specifications (F-001 through F-016)
│ ├── ROADMAP.md # Current priorities
│ ├── RESEARCH.md # Research findings & competitor analysis
│ ├── VISION.md # Project vision
│ └── research/ # Deep-dive research topics
├── CLAUDE.md # This file — agent development guide
└── README.md # Project overview
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.
- 3d ago First seen · 138 lines · 1,874 tokens per session scan B 1b20ed34e240
autonomOS AGENTS.md is an instructions file published in the GitHub repository aterrylu/autonomOS (5 stars, last pushed 3d ago), licensed MIT. It adds 1,874 tokens to every session, about $0.0094 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
helmor AGENTS.md
Instructions for dohooo/helmor, covering agents.md, what is helmor, commands, architecture and three-process model.
zeroshot AGENTS.md
AGENTS.md instructions for the-open-engine/zeroshot, covering zeroshot: multi-agent coordination engine, critical rules, where to look, cluster worker contracts and cli quick reference.
claudectl CLAUDE.md
Instructions for mercurialsolo/claudectl, covering claudectl, build & test, architecture, workspace layout and core modules — claudectl-core (crates/claudectl-core/src/).
agents CLAUDE.md
Instructions for eloylp/agents, covering claude.md, project overview, directory structure, config model and build & run.
agiwo AGENTS.md
Instructions for xhwSkhizein/agiwo, covering agents.md, how to use this file, truth source order (adr 0048 / 0049), logging and config hot reload.
Agent-Harness-Kit AGENTS.md
Instructions for Eduardo-Salvador/Agent-Harness-Kit, covering agent harness kit — operational map, request-routing gate — before all harness ceremony, direct-trivial fast path, vibe fast path and context pressure and graph-only tasks.