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/ahepi/deepreason/claude-mdgit clone --depth 1 https://github.com/AHepi/DeepReasonWhat 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.08902 | $0.08902 |
| Opus 5 | $0.04451 | $0.04451 |
| Sonnet 5 | $0.01780 | $0.01780 |
| Haiku 4.5 | $0.00890 | $0.00890 |
Grade A, and why
DeepReason 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 — 636 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — operating DeepReason
DeepReason is a Popperian reasoning harness: it drives a provider model
(currently glm-5.2 on Ollama Cloud) through conjecture–criticism cycles
over an append-only, replay-verifiable record. Everything meaningful is
TYPED — stops, denials, refusals, capability lifecycles — and the record
is the only admissible evidence about what a run did. Model prose is
never evidence; log.jsonl, objects/, progress.jsonl,
run-status.json, REPLAY_VALIDATION.json, and verify_root are.
Which workflow to use
Both families now begin with a MAP PREFLIGHT: resolve the work to
DR-SUB-/DR-CON-/DR-SEAM- ids from docs/map/INDEX.md, read the seam
before the subsystems, and read INV-frozen-surfaces.md before designing.
Record the ids in the tranche's first artifact so every later phase starts
from the same map.
Two skill families live in .claude/skills/. Route ALL substantive work
through one of them — they exist to prevent scope creep, missed steps,
and forgotten inputs:
-
Something is broken / suspicious →
deepreason-orchestrator(phases: dr-set-goal → dr-diagnose → dr-reproduce → dr-propose-fix → dr-implement-fix → dr-verify-outcome). Diagnosis comes from the typed record BEFORE code reading. -
The operator suggests a change →
dr-change-orchestrator(phases: dr-capture-request → dr-spec-change → dr-plan-steps → dr-execute-step (one step per invocation) → dr-validate-change → dr-deliver-change). Authority is the operator's verbatim words, ledgered in REQUEST.md; every artifact traces to requirement numbers. -
The operator asks what is broken / unused / out of date →
dr-audit-orchestrator(dimensions: broken, dead, docs-drift, spec-drift, goal-trace). Read-only: produces AUDIT_REPORT.md plus a ready-to-send fix prompt per finding; every verdict compares againstdocs/AUDIT_BASELINES.md. Rated for inexpensive models — every step is a command, a paste, or a baseline comparison.
Cross-routing: a defect found mid-change is PARKED, not fixed; a change wished for mid-defect is PARKED, not implemented. One tranche, one goal. The audit family never fixes anything anywhere — findings become parked prompts for the other two families.
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 · 636 lines · 8,902 tokens per session scan A 73c4ebf494f3
DeepReason CLAUDE.md is an instructions file published in the GitHub repository AHepi/DeepReason (140 stars, last pushed 2d ago), licensed MIT. It adds 8,902 tokens to every session, about $0.0445 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
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
airi copilot-instructions.md
Copilot instructions for moeru-ai/airi, covering copilot repository instructions, general rules, validation and output format.
n8n-skills CLAUDE.md
Instructions for czlonkowski/n8n-skills, covering claude.md, project overview, repository structure, the 14 skills and 1. n8n expression syntax.
entroly CLAUDE.md
Instructions for juyterman1000/entroly, covering claude.md, gstack operating protocol, default workflow, entroly trust invariants and review checklist.
Sponsio CLAUDE.md
Instructions for SponsioLabs/Sponsio, covering agent guide for sponsio, what sponsio is, positioning, what to read first and repository map.
autonomous-os AGENTS.md
Instructions for autonomous-ai/autonomous-os, covering agents.md, multi-ide rules, working style, parallel work / subagents and device access rules.