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/claude-mdgit clone --depth 1 https://github.com/aterrylu/autonomOSWrote 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/aterrylu/autonomos/claude-md)<a href="https://agentmods.dev/instructions/aterrylu/autonomos/claude-md"><img src="https://agentmods.dev/badge/instructions/aterrylu/autonomos/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 | $0.07311 | $0.07311 |
| Opus 5 | $0.03655 | $0.03655 |
| Sonnet 5 | $0.01462 | $0.01462 |
| Haiku 4.5 | $0.00731 | $0.00731 |
Grade C, and why
autonomOS CLAUDE.md scanned grade C with 3 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 5d 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 ( Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**The `isolated` mode was REMOVED** (spawned a headless `claude -p`). It was the one execution path in the product outside `PermissionMode`, and it was fail-open in three places at once: the executor's `autonomous !== fa 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 — 214 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/ # dockview tabs + split panes (ADR-047, the only layout engine)
│ ├── 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.
- 5d ago First seen · 214 lines · 7,311 tokens per session scan C aadfaf62e973
autonomOS CLAUDE.md is an instructions file published in the GitHub repository aterrylu/autonomOS (5 stars, last pushed 5d ago), licensed MIT. It adds 7,311 tokens to every session, about $0.0366 per session on Opus 5. A static security scan graded it C with 3 findings (sends data to an external url, reads agent configuration directories, 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
kungfu copilot-instructions.md
Copilot instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before proposing or running changes. It is the shared agent router for this repository, including the canonical Shifu development and build entrypoint.
agents CLAUDE.md
Instructions for eloylp/agents, covering claude.md, project overview, directory structure, config model and build & run.
ideate AGENTS.md
Instructions for paultyng/ideate, covering agents.md, build features as mcp tools first, ui second, when to add ui and pattern.
omk CLAUDE.md
Claude Code instructions for dmae97/omk, covering claude.md, precedence (read this first), omk runtime map (what you're operating inside), this repo: open-multi-agent-kit / omk monorepo and build / test / check commands.
icron CLAUDE.md
Instructions for zebbern/icron, covering icron, architecture, key directories, built-in tools and commands.
workstreams disposable.instructions.md
Guidelines for writing code using IDisposable.