dory CLAUDE.md

A set of project instructions for Claude coding agents working on the public Dory code repository. It covers how agents should operate, follow codebase rules, protect private information, and handle commits and pull requests.

In plain words
What is it for?
Following Dory’s search and session practices, checking Python changes with Ruff and pytest, and handling OpenClaw plugin updates, commits, and pull requests.
Why use it?
It gives agents consistent project-specific guidance instead of making them infer rules from scattered files. It also helps prevent private data from being copied into public project materials.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/deeflect/dory/claude-md
Clone the repo
git clone --depth 1 https://github.com/deeflect/dory
Per session 492 This file is loaded in full into every session.
When invoked 492 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 92b735eb805f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

CLAUDE.md · 33 lines

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_search followed by exact dory_get before 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; use uv run pytest -q when the change has broad impact.
  • For OpenClaw plugin changes, update packages/openclaw-dory/src/index.ts, run npm install && npm run build locally or npm ci && npm run build in CI, and include the rebuilt packages/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 like example.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 guide or fix(search): rank canonical hits first.
  • Include verification in the final response and in PR notes.
  • Mention any skipped checks explicitly.

Read the full file on GitHub · 33 lines

Changes

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.

  1. 2d ago First seen · 33 lines · 492 tokens per session scan A 92b735eb805f

Subscribe to this mod's changes

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.