Borrowing it
Nothing to install: this file belongs to sentasity/cadence. 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/sentasity/cadence/main/CLAUDE.mdgit clone --depth 1 https://github.com/sentasity/cadenceWrote 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/sentasity/cadence/claude-md)<a href="https://agentmods.dev/instructions/sentasity/cadence/claude-md"><img src="https://agentmods.dev/badge/instructions/sentasity/cadence/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/sentasity/cadence/claude-md"><img src="https://agentmods.dev/badge/instructions/sentasity/cadence/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.00324 | $0.00324 |
| Opus 5.5 | $0.00130 | $0.00130 |
| Sonnet 5.5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
cadence 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 19d 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.
What it actually says
Cadence repo conventions
Config reads go through the resolver
Skill and agent text in this repo must route every Cadence config read through scripts/resolve-config.js (invoked as node "${CLAUDE_PLUGIN_ROOT}/scripts/resolve-config.js"). Never write skill or agent text that instructs a direct read of .cadence/config.yaml, .cadence/config.local.yaml, or defaults/config.default.yaml — prose resolution is exactly the failure the resolver exists to remove. The contract (output shape, exit codes, hard-stop rule, sanctioned write paths) lives in skills/_shared/config-resolution.md.
Tests
node --test 'scripts/*.test.js' runs the Node script suites (migrate-config.test.js, resolve-config.test.js, notion-rest.test.js, notion-write.test.js, notion-read.test.js, and skill-structure.test.js, which checks the shipped skill and agent text), and bash scripts/test-merge-lock.sh smoke-tests merge-lock.sh. Run both before any PR that touches scripts/, skills/, agents/, or templates/.
Skill descriptions
A skill's description: frontmatter says only when to use the skill: it starts with "Use when", stays under 250 characters, and never summarizes the workflow. An agent that reads a workflow summary in the description can follow it instead of the skill body. Guarantees ("never writes code") belong in the body. scripts/skill-structure.test.js enforces the shape.
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.
- 19d ago Changed · +14 tokens per session 29afa63af58f
- 1mo ago Changed · +4 lines · +132 tokens per session 8001bde72b59
- 2mo ago First seen · 10 lines · 178 tokens per session scan A 9611986ebc4c
cadence CLAUDE.md is an instructions file published in the GitHub repository sentasity/cadence (1 stars, last pushed 19d ago), licensed MIT. It adds 324 tokens to every session, about $0.0013 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
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.