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/jeomon/operator-use/claude-mdgit clone --depth 1 https://github.com/Jeomon/Operator-UseWrote 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/jeomon/operator-use/claude-md)<a href="https://agentmods.dev/instructions/jeomon/operator-use/claude-md"><img src="https://agentmods.dev/badge/instructions/jeomon/operator-use/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.01675 | $0.01675 |
| Opus 5 | $0.00838 | $0.00838 |
| Sonnet 5 | $0.00335 | $0.00335 |
| Haiku 4.5 | $0.00168 | $0.00168 |
Grade A, and why
Operator-Use 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 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.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operator — CLAUDE.md
Top-level guidance for Claude Code when working on this repository.
Project Overview
Operator is a stateful Python AI agent harness. It wraps a multi-provider LLM inference layer with session persistence, context compaction, an extension/package system, sandbox enforcement, browser/computer automation, and a gateway that connects the agent to multiple messaging channels simultaneously (Telegram, Discord, Slack, WebSocket, Email, Twitch, stdio).
Four layers build on each other:
- Engine (
operator_use/engine/) — raw LLM streaming loop, tool execution, abort signal. No knowledge of sessions or extensions. - Agent (
operator_use/agent/) — turn orchestration, retry, compaction scheduling, extension event fan-out. ImplementsExtensionContext. - Runtime (
operator_use/runtime/) — session lifecycle, slash-command dispatch, gateway/cron/subagent wiring. - Gateway (
operator_use/gateway/) — channel adapters, async message bus, per-session agent routing.
Repository Layout
operator_use/
agent/ engine/ session/ runtime/
extension/ hooks/ resource/ gateway/
inference/ settings/ package/ builtins/
compaction/ subagent/ cron/ process/
mcp/ acp/ auth/ tool/
skill/ commands/ message/ prompt/
browser/ computer/ peer/ team/
workflow/ knowledge/ sandbox/ diagnostics/
memory/ bus/ console/ templates/
tests/
docs/ ← read these before exploring code
Quick Navigation
Find detailed documentation before reading source:
| Need to understand… | Read |
|---|---|
| Full system — channels → gateway → agent → engine → session | docs/architecture.md |
| Turn flow, retry, compaction scheduling | docs/agent.md |
| Guardrail interface, loading, loop detection | docs/guardrails.md |
| LLM loop, tool execution modes, queues | docs/engine.md |
| Session JSONL, branching, reconstruction | docs/session.md |
Extension loading, api.config, dispatch |
docs/extensions.md |
Package install, operator.json, wiring |
docs/packages.md |
| Event types, hook registration | docs/hooks.md |
| Channels, message bus, stream phases | docs/gateway.md |
| Models, providers, auth | docs/inference.md |
| Tool interface, execution modes | docs/tool.md |
| SKILL.md format, discovery | docs/skill.md |
| Slash commands, builtin commands | docs/commands.md |
| Credentials, OAuth, token refresh | docs/auth.md |
| Named profiles, AGENT.md format | docs/profiles.md |
| Browser automation via CDP | docs/browser.md |
| Desktop computer control | docs/computer.md |
| Sandbox policy, OS-level isolation | docs/sandbox.md |
| Knowledge base, document injection | docs/knowledge.md |
| Multi-agent teams, mailboxes | docs/team.md |
| Python workflows, DSL globals | docs/workflow.md |
| ACP transports, server/client | docs/acp.md |
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 · 142 lines · 1,675 tokens per session scan A 7645efd99bae
Operator-Use CLAUDE.md is an instructions file published in the GitHub repository Jeomon/Operator-Use (40 stars, last pushed 2mo ago), licensed MIT. It adds 1,675 tokens to every session, about $0.0084 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
SmolVM AGENTS.md
Instructions for CelestoAI/SmolVM, covering smolvm context, 🚀 project overview, 🧪 development, key commands and release checklist.
SmolVM CLAUDE.md
Instructions for CelestoAI/SmolVM, a project described as: Open-source AI sandbox infrastructure with unified API for VMMs -- Firecracker, QEMU and libkrun.
lobu AGENTS.md
Instructions for lobu-ai/lobu, covering repo map, unrecoverable — never do these, facts you cannot derive, ship a change and how to work.
lobu CLAUDE.md
Instructions for lobu-ai/lobu, a project described as: Open-source control plane and runtime for organisational agents: shared company context, isolated execution, approvals and MCP.
librefang AGENTS.md
Instructions for librefang/librefang, covering stack, layout, build, architecture and kernelhandle trait.
openclaw CLAUDE.md
Claude Code instructions for openclaw/openclaw, a project described as: Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞.