Borrowing it
Nothing to install: this file belongs to dharma-okf-foundation/dharma-okf. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dharma-okf-foundation/dharma-okf/main/CLAUDE.mdgit clone --depth 1 https://github.com/dharma-okf-foundation/dharma-okfWrote 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/dharma-okf-foundation/dharma-okf/claude-md)<a href="https://agentmods.dev/instructions/dharma-okf-foundation/dharma-okf/claude-md"><img src="https://agentmods.dev/badge/instructions/dharma-okf-foundation/dharma-okf/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/dharma-okf-foundation/dharma-okf/claude-md"><img src="https://agentmods.dev/badge/instructions/dharma-okf-foundation/dharma-okf/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01981 | $0.01981 |
| Opus 5 | $0.00991 | $0.00991 |
| Sonnet 5 | $0.00396 | $0.00396 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
dharma-okf 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dharma-okf — agent working rules
This repository publishes Dharma-OKF, a profile of the Open Knowledge Format. Read PROFILE.md before changing anything; it is normative and this file is its operational summary. Where the two disagree, PROFILE.md wins and this file is the bug.
Base spec: OKF v0.2 at GoogleCloudPlatform/open-knowledge-format@ad30107. Profile: dharma-okf/1.0.
Corpus: 442 concept documents in 13 bundles — 310 type: Concept, 132 type: Reference.
The one thing to understand first
On OKF v0.2, the specification and the reference implementation disagree. Reading SPEC.md alone will lead you to author bundles that upstream's own tooling silently mishandles. Every rule below marked ⚠️ exists because of a specific divergence that was verified by reading upstream source, not upstream prose. Do not "correct" them back toward the spec text.
Never
These are refusals. If a task appears to require one, stop and ask.
- Never write
verified:. It records a human review event by a tradition-bearer. Automated tooling writesgenerated:and nothing else. Stampingverified:during a mechanical edit asserts that a person checked a document no person checked — it converts the corpus's central trust claim into noise. (PROFILE.md§3.3) - Never flatten
not:to a list of strings. Theterm/why/insteadtriple is the payload, not decoration.whyis the argument;insteadis what a consuming agent actually executes as a prompt or filter constraint. A bare["Fate", "Destiny"]is the abandoned v0.1 shape and destroys the field's function across 310 files. (§2.1) - Never delete
## Citationsbody sections or their links when addingsources:frontmatter. Body links are the only source of graph edges —related:frontmatter is not traversed by link-graph consumers. Removing them silently deletes the bundle's relationship graph. Frontmattersourcesis added alongside, never migrated from. (§2.5, §3.1) - Never claim another producer's identity in
generated.by.reference_agent/...is Google's. Use your own namespace:claude-opus-5/<version>,gemini-spark/<version>. (§2.3, base §7) - Never change a document's
type:value. It isConceptorReference. Both are load-bearing:Referenceis colour-matched by upstream's viewer, and the split is what makesnot:-applicability checkable. (§1) - Never edit files under a release tag's assumptions.
mainis the living vocabulary; tags are immutable snapshots. Content revisions patch-bumpbundle_versionand append toCHANGELOG.md. SeeVERSIONING.md.
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 Changed · +6 tokens per session b33f0a16b2a8
- 3d ago Changed · +41 tokens per session 6931af8f1056
- 9d ago First seen · 135 lines · 1,934 tokens per session scan A 5e81d30ecc6c
dharma-okf CLAUDE.md is an instructions file published in the GitHub repository dharma-okf-foundation/dharma-okf (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,981 tokens to every session, about $0.0099 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.