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/sbusso/claudeclaw/claude-mdgit clone --depth 1 https://github.com/sbusso/claudeclawWrote 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/sbusso/claudeclaw/claude-md)<a href="https://agentmods.dev/instructions/sbusso/claudeclaw/claude-md"><img src="https://agentmods.dev/badge/instructions/sbusso/claudeclaw/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.03201 | $0.03201 |
| Opus 5 | $0.01600 | $0.01600 |
| Sonnet 5 | $0.00640 | $0.00640 |
| Haiku 4.5 | $0.00320 | $0.00320 |
Grade A, and why
claudeclaw CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:3100/webhook/mygroup \ How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClaudeClaw
Persistent agent orchestrator plugin for Claude Code.
Entry Points
Two separate entry points — plugin and service must not be conflated:
src/index.ts→dist/index.js— Plugin entry. Loaded by Claude Code via--plugin-dir. Returns immediately, no side effects. No channel/extension imports.src/service.ts→dist/service.js— Service entry. Run by launchd/systemd as persistent background process. Imports channels/extensions, starts the message loop.
The plugin entry is what .claude-plugin/plugin.json points to. The service entry is what npm start, npm run dev, and the launchd plist/systemd unit run.
Modes
ClaudeClaw runs in two modes, detected by .claude-plugin/plugin.json in cwd:
Plugin mode (no .claude-plugin/ in cwd):
- Loaded via
claude --plugin-dir /path/to/claudeclaw - Current directory IS the instance — all state lives in cwd
- No hidden paths, no
~/.claude/plugin-data/ - Multiple instances = multiple directories (
cdis the instance switcher) - Service per directory:
com.claudeclaw.<dirname>.plist(macOS),claudeclaw-<dirname>.service(Linux) - Upgrade to developer mode: clone the repo INTO the data directory
Developer mode (.claude-plugin/plugin.json exists in cwd):
- Cloned repo,
clauderuns from inside it - Code and state in the same directory
- Full self-improvement — Claude edits its own source
- Git/fork workflow
Directory = Instance
No instance manager. No switching commands. The directory you run claude from IS the ClaudeClaw instance.
~/assistants/personal/ ← one instance (cd here, run claude)
.env, store/, groups/, logs/, .claudeclaw.json
~/assistants/work/ ← another instance
.env, store/, groups/, logs/, .claudeclaw.json
Path resolution: STATE_ROOT = process.cwd() always. STORE_DIR, GROUPS_DIR, LOG_DIR derive from it. readEnvFile() checks CLAUDECLAW_ENV_FILE then cwd/.env.
Architecture
src/
index.ts # Plugin entry (Claude Code --plugin-dir, non-blocking)
service.ts # Service entry (launchd/systemd, runs message loop)
orchestrator/ # Core
message-loop.ts # THE HEART: poll, trigger, thread, queue, dispatch
group-queue.ts # Concurrency control for agent execution
extensions.ts # Pluggable extension system (registerExtension API)
extension-loader.ts # Scans extensions/ dir, loads manifests, dynamic imports
extension-manifest.ts # Manifest schema + validation
channel-registry.ts # Channel self-registration
ingestion.ts # Inbound message processing (pre/post hooks)
outbound-router.ts # Outbound message routing (pre/post hooks)
db.ts # SQLite with extension schema support
config.ts # Core config (from .env)
env.ts # .env reader
logger.ts # Pino logger
types.ts # Core types (Channel, RegisteredGroup, NewMessage)
runtimes/ # Agent execution backends
container-runtime.ts # Container runtime abstraction (binary detection, lifecycle)
container-runner.ts # Container-based agent runner (Docker/Apple Container)
sandbox-runner.ts # Sandbox-based agent runner (srt, OS-level sandboxing)
channels/ # Built-in channels (whatsapp, telegram)
cost-tracking/ # Built-in: token usage + cost estimation
webhook/ # Built-in: HTTP webhook triggers
extensions/ # Installable extensions (gitignored, per-instance)
claudeclaw-slack/ # Slack channel (install with /install slack)
claudeclaw-triage/ # Triage + SWE agents (install with /install triage)
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 · 267 lines · 3,201 tokens per session scan A df42607fbf77
claudeclaw CLAUDE.md is an instructions file published in the GitHub repository sbusso/claudeclaw (193 stars, last pushed 23d ago), licensed MIT. It adds 3,201 tokens to every session, about $0.0160 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
atlasclaw AGENTS.md
AGENTS.md instructions for CloudChef/atlasclaw, covering agents.md - atlasclaw coding guidelines, build / test / lint commands, backend (python), run the service and run all tests.
atlasclaw CLAUDE.md
Claude Code instructions for CloudChef/atlasclaw, covering openspec instructions, language preference and workflow.
mini-swe-agent copilot-instructions.md
Copilot instructions for SWE-agent/mini-swe-agent, covering style guide, test style, bad and good.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
agent-skills-standard CLAUDE.md
Claude Code instructions for HoangNguyen0403/agent-skills-standard, covering agent protocol and self-learning protocol.
lime AGENTS.md
AGENTS.md instructions for limecloud/lime, covering lime 源码仓库指南, 事实源, 工程约束, 协议与质量 and 执行方式.