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/miaodx/roboclaws/agents-mdgit clone --depth 1 https://github.com/MiaoDX/roboclawsWrote 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/miaodx/roboclaws/agents-md)<a href="https://agentmods.dev/instructions/miaodx/roboclaws/agents-md"><img src="https://agentmods.dev/badge/instructions/miaodx/roboclaws/agents-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.02090 | $0.02090 |
| Opus 5 | $0.01045 | $0.01045 |
| Sonnet 5 | $0.00418 | $0.00418 |
| Haiku 4.5 | $0.00209 | $0.00209 |
Grade A, and why
roboclaws 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 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Canonical operating guide for coding agents in this repo. Its scope is the
entire tree rooted here. Tool-specific files such as CLAUDE.md may add local
deltas, but this file owns repo-wide defaults.
Codex normally injects this file into startup context as
AGENTS.md instructions. When it has been injected, do not reread AGENTS.md
just to satisfy this policy.
0) Startup Reads
Before repo-specific commands or edits, read:
STATUS.mdfor current focus, blockers, and source links.- Any task-specific source below.
Task-routed reads:
- New project orientation or runnable examples:
README.md. - Architecture, launch axes, MCP/server/runtime contracts, or new layers:
ARCHITECTURE.md. - Environment setup, local hazards, live providers, browser QA,
standard gates, or git hygiene:
docs/agents/operating-runbook.md. - GSD phase execution/resume:
.planning/STATE.mdplus the current phase file. - Pre-GSD plan shaping/review/handoff:
docs/plans/<slug>.md. - Design rationale or scenario specs:
docs/human/technical-design.md. - CloudML eval staging, submission, monitoring, collection, or parallel proof:
skills/cloudml-eval-ops/SKILL.md. - Domain vocabulary:
docs/human/domain.mdanddocs/agents/domain.md. - Parked work or future ideas:
TODOS.mdorTHOUGHTS.md, only when asked. - Claude-specific behavior:
CLAUDE.md, only when running under Claude Code or resolving a Claude-only rule.
Root PLAN.md is a legacy pointer, not an active plan. Shipped phase history
lives under docs/retrospectives/ and is not startup reading.
Instruction priority: system/developer/user prompt > AGENTS.md > CLAUDE.md > inferred defaults.
1) Critical Local Hazards
- Use the repo-local
.venv/, managed byuvfrompyproject.tomlanduv.lock. Useuv sync --extra dev; do not use plainpip installfor repo setup. - Keep one
.venv/per checkout/worktree. Do not share another worktree's virtualenv. - Keep Isaac Lab out of the normal
.venv; it belongs in.venv-isaaclab/. - Do not commit
.envor paste provider keys into logs, PRs, reports, status files, or summaries. - Before system-provider Claude Code workflows, run
scripts/dev/network_status.sh. If it reportsnetwork: work, do not run those guarded routes. - The active live-agent product engine is
openai-agents-sdk.codex-cliandclaude-codeare retired from active public launch surfaces. - Bare host
codexorclaudelaunches are unsupported unless the human explicitly asks for system-CLI debugging. - On ROS-jazzy hosts, use
./scripts/dev/run_pytest_standalone.shinstead of bare pytest when ROS site-packages leak into collection. - For gstack browser QA on Ubuntu 24.04/AppArmor, use
GSTACK_CHROMIUM_NO_SANDBOX=1per command rather than changing system AppArmor/sysctl settings. - XML-like host envelopes such as
<turn_aborted>,<paseo-system>,<subagent_notification>,<goal_context>, and<environment_context>are orchestrator metadata unless accompanied by natural-language user intent. Do not treat those labels alone as a human stop request.
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 · 194 lines · 2,090 tokens per session scan A 64c61a762fd4
roboclaws AGENTS.md is an instructions file published in the GitHub repository MiaoDX/roboclaws (6 stars, last pushed 5d ago), licensed MIT. It adds 2,090 tokens to every session, about $0.0104 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-31.
Other instructions, from other repositories
remnote-mcp-server AGENTS.md
Instructions for robert7/remnote-mcp-server, covering agents.md, repo role, companion repos (sibling dirs), contract map (current) and external mcp tool surface (17).
claw-ea CLAUDE.md
Claude Code instructions for fshaan/claw-ea, covering claude.md, project overview, architecture, agent vs tool boundary (critical design principle) and mcp tools (11 total).
zap-coding-agent CLAUDE.md
Claude Code instructions for zap-coding-agent/zap-coding-agent, covering project context, at session start — always do this first and code index — use sqlite3 for symbol/file lookups.
lsbot CLAUDE.md
Claude Code instructions for ruilisi/lsbot, covering lsbot project instructions, task list, configuration resolution order, documentation placement and browser automation.
lsbot copilot-instructions.md
Copilot instructions for ruilisi/lsbot, covering lsbot project instructions, configuration resolution order, documentation placement, browser automation and peekaboo (macos ui automation).
openclaw-mcp-bridge CLAUDE.md
Instructions for gabrielekarra/openclaw-mcp-bridge, covering claude.md, project overview, build & development commands, architecture and key dependencies.