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/deeflect/dory/claude-mdgit clone --depth 1 https://github.com/deeflect/doryWhat 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.00492 | $0.00492 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
dory 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 2d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Agent Guide
Claude agents should follow AGENTS.md. This file adds Claude-specific reminders for working in the public Dory repository.
Operating Mode
- Use Dory MCP tools directly when available. Start a new session, post-compaction continuation, or real task switch with
dory_wake(profile="coding", budget_tokens=1200)for code work; do not rerun wake on every turn when the wake block is still in context. - Prefer
dory_searchfollowed by exactdory_getbefore making claims about project state, prior decisions, or current runtime assumptions. - Do not copy private Dory memory into repository files. Public docs, tests, evals, examples, and issue templates must use synthetic data.
- Keep responses and patches scoped. If a change is cross-cutting, state the plan briefly and then implement.
Codebase Norms
- Python code targets Python 3.12 and is managed with
uv. - Run
uv run ruff check <paths>for touched Python paths. - Run focused
uv run pytest ...tests for behavior changes; useuv run pytest -qwhen the change has broad impact. - For OpenClaw plugin changes, update
packages/openclaw-dory/src/index.ts, runnpm install && npm run buildlocally ornpm ci && npm run buildin CI, and include the rebuiltpackages/openclaw-dory/dist/index.js. - Do not edit generated or local runtime files unless the task explicitly asks for them.
Public-Safety Rules
- No real tokens, API keys, bearer values, private hostnames, personal identifiers, or local absolute paths.
- No real private memories in fixtures. Use names like
Atlas,Demo User,Example Project, and placeholder domains likeexample.com. - Do not add raw session logs or private corpus material to the public tree.
- Run
uv run python scripts/release/check-public-safety.py --path <path>for changed public docs, fixtures, evals, examples, or release artifacts.
Commit And PR Rules
- Only commit when the user asks.
- Use Conventional Commits with a clear scope when useful, for example
docs: add contribution guideorfix(search): rank canonical hits first. - Include verification in the final response and in PR notes.
- Mention any skipped checks explicitly.
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.
- 2d ago First seen · 33 lines · 492 tokens per session scan A 92b735eb805f
dory CLAUDE.md is an instructions file published in the GitHub repository deeflect/dory (11 stars, last pushed 2mo ago), licensed MIT. It adds 492 tokens to every session, about $0.0025 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
microsandbox AGENTS.md
AGENTS.md instructions for superradcompany/microsandbox, covering agents.md, scope, project map, design principles and backward compatibility review.
full-stack-ai-agent-template CLAUDE.md
Instructions for vstorm-co/full-stack-ai-agent-template, covering claude.md, project overview, commands, install dependencies and run tests.
MultiGen CLAUDE.md
Instructions for lingyuanli/MultiGen, covering claude.md, architecture, development commands, full stack (docker) and api (local).
ILLIP AGENTS.md
Instructions for Yashwanth-pilli/ILLIP, covering illip ai - agent framework documentation, agents, 1. planner agent, 2. builder agent and 3. reviewer agent.
pulse8-ai-cortex-knowledge-vault AGENTS.md
Instructions for synpulse8-opensource/pulse8-ai-cortex-knowledge-vault, covering agents.md — pulse8.ai cortex, repository map, environment variables, essential commands and dependencies.
GooFish-AIMonitor AGENTS.md
Instructions for tristanwqy/GooFish-AIMonitor, covering agents.md — 给 ai 协作者的工程指南, 黄金规则(先读这条), 验证命令(完成前必跑), 代码地图 and 数据模型要点.