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/ucsandman/dashclaw/claude-mdgit clone --depth 1 https://github.com/ucsandman/DashClawWrote 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/ucsandman/dashclaw/claude-md)<a href="https://agentmods.dev/instructions/ucsandman/dashclaw/claude-md"><img src="https://agentmods.dev/badge/instructions/ucsandman/dashclaw/claude-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.03516 | $0.03516 |
| Opus 5 | $0.01758 | $0.01758 |
| Sonnet 5 | $0.00703 | $0.00703 |
| Haiku 4.5 | $0.00352 | $0.00352 |
Grade A, and why
DashClaw 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 4d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DashClaw (v2 Governance Runtime)
DashClaw is AI agent decision infrastructure: a focused control plane for policy enforcement, decision recording, assumption tracking, and risk signals.
Commands
npm run dev # local dev server (port 3000)
npm run lint # eslint
npm run typecheck # tsc --noEmit — required for any changed .ts file, even outside app/
npm test # vitest; one file: npm test -- <file> (full suite before push: npx vitest run)
npm run build # next build — required for any change under app/**
npm run db:migrate # apply pending schema to local DB (auto-loads .env.local; idempotent)
All other scripts stay in package.json; add one here only when the agent keeps needing it.
Verify before you commit
CLAUDE.md is advisory; CI is not. A push is its own step - run these and READ the output first:
npm run lintnpx vitest run- the full suite (targeted runs miss regressions in unrelated files)npx next build- required for any change underapp/**- For any changed
.tsfile (even outsideapp/), runnpm run typecheckbefore pushing - vitest transpiles without type-checking and will pass; the build runstscand will not. - Entry-path drills (v8.3,
scripts/drills/README.md): a release touchingcli/**,scripts/setup.mjs, or theuppath runsnpm run drill:fresh-windows(and/ordrill:fresh-linux) first; one touching hosted mint/export/import runsnpm run drill:hosted. A drill failure is a broken ship - fix on the spot, log it in the maintainer log. These test the DISTRIBUTION path on factory-fresh machines; CI'sup-smoke.yml(from-source, dev-imaged runners) does not cover that class.
CI also gates openapi:check, api:inventory:check, route-sql:check, and version:check. The pre-commit hook lints staged JS/TS, typechecks when a staged file is .ts/.tsx, and regenerates the doc/contract/bundle artifacts for you (see "Generated artifacts").
Session discipline (from usage-log audit, 2026-08-03):
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.
- 4d ago First seen · 172 lines · 3,516 tokens per session scan A 311e31f6c1d6
DashClaw CLAUDE.md is an instructions file published in the GitHub repository ucsandman/DashClaw (295 stars, last pushed today), licensed MIT. It adds 3,516 tokens to every session, about $0.0176 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
holon AGENTS.md
AGENTS.md instructions for holon-run/holon, covering repository guidelines, project structure & module organization, product intent, development priorities and coding style & naming conventions.
Jixu AGENTS.md
Instructions for joe960913/Jixu, covering jixu repository instructions, 1. read order, 2. sources of truth, 3. canonical concepts and 4. architecture invariants.
holon CLAUDE.md
Claude Code instructions for holon-run/holon: This file is read by Claude Code and other agent tooling.
kdcube AGENTS.md
AGENTS.md instructions for kdcube/kdcube, covering agents.md — operating rules for coding agents, shared ground rules (both classes), a. platform contributors, git and shared-tree etiquette and code architecture.
Core-Memory CLAUDE.md
Instructions for JohnnyFiv3r/Core-Memory, covering claude.md — core memory, what this repo is, guiding principle — engineering simplicity, boring primitives, rich views and mapping to the current codebase.
OpenMAO AGENTS.md
Instructions for OpenMAO/OpenMAO, covering agents.md - openmao agent protocol, start here, stay on course, hard rules and working protocol.