Borrowing it
Nothing to install: this file belongs to brysontang/domino. 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/brysontang/domino/main/CLAUDE.mdgit clone --depth 1 https://github.com/brysontang/dominoWrote 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/brysontang/domino/claude-md)<a href="https://agentmods.dev/instructions/brysontang/domino/claude-md"><img src="https://agentmods.dev/badge/instructions/brysontang/domino/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/brysontang/domino/claude-md"><img src="https://agentmods.dev/badge/instructions/brysontang/domino/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.00979 | $0.00979 |
| Opus 5 | $0.00490 | $0.00490 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
domino 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 9d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault
This is the task vault. The file system is the instruction set.
Philosophy
There is no orchestration daemon. No database. No custom scripts. Just mv, find, grep, and CLAUDE.md doing what it already does natively.
Moving a folder IS the orchestration:
mv epics/planning/my-epic epics/active/→ Epic is greenlit, agents can workmv backlog/story.md active/→ Story is claimed, work beginsmv active/story.md in-review/→ Implementation done, awaiting reviewmv epics/active/my-epic epics/done/→ Epic shipped
You walk into a folder and become the right agent for that context.
Structure
domino/
├── phases/ # Canonical instructions (single source of truth)
├── templates/ # Dash/epic/story/contract templates (use @ imports)
├── epics/ # Single epics
│ ├── backlog/ — epics waiting to be planned
│ ├── planning/ — epics being specced
│ ├── active/ — epics approved for execution
│ └── done/ — shipped epics (historical reference)
└── dashes/ # Multi-epic pushes (shorter than a sprint)
├── backlog/ — dashes waiting to be planned
├── planning/ — epics specced in isolation, then woven into one graph
├── active/ — dashes approved for execution
└── done/ — shipped dashes
A dash is a folder of epics shipped together, plus contracts/ — frozen
interface docs that let the epics run in parallel. Cross-epic dependencies are
story-level edges in dash.md; every edge must cite a contract.
Creating Work
New epic:
cp -r templates/epic epics/backlog/my-epic-name
# Edit epics/backlog/my-epic-name/epic.md with vision
New story:
cp templates/story.md epics/planning/my-epic/backlog/01-story-name.md
# Edit with acceptance criteria
New dash:
cp -r templates/dash dashes/backlog/my-dash-name
# Edit dash.md with vision — epics get split out during planning
Navigation
- Each epic is a folder containing
epic.mdand story subfolders - Stories live in:
backlog/,active/,in-review/,completed/ - Find active stories:
find epics/active/ -path "*/active/*.md" ! -name "CLAUDE.md" - Find by system:
grep -rl "systems:.*jwt" epics/ dashes/ - Find a contract's consumers:
grep -rl "contracts:.*jwt-claims" dashes/
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.
- 9d ago First seen · 96 lines · 979 tokens per session scan A cf410a55d6d3
domino CLAUDE.md is an instructions file published in the GitHub repository brysontang/domino (2 stars, last pushed 1mo ago), licensed MIT. It adds 979 tokens to every session, about $0.0049 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.