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/chadbyte/clay/claude-mdgit clone --depth 1 https://github.com/chadbyte/clayWhat 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.00525 | $0.00525 |
| Opus 5 | $0.00262 | $0.00262 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
clay 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.
What it actually says
Project Rules
- Never add
Co-Authored-Bylines to git commit messages. - Use
varinstead ofconst/let. No arrow functions. - Server-side: CommonJS (
require). Client-side: ES modules (import). - Never commit, create PRs, merge, or comment on issues automatically. Only do these when explicitly asked.
- All user-facing messages, code comments, and commit messages must be in English only.
- Every commit must strictly follow the Angular Commit Convention. This requirement is mandatory with no exceptions, including small fixes, generated changes, and follow-up commits.
- When the user explicitly requests a commit, always invoke and follow the
angular-commitskill before staging or committing. Never rungit commitwithout using that skill. - Commit subjects must use either
<type>: <summary>or<type>(<scope>): <summary>, wheretypeis one offeat,fix,docs,chore,refactor,perf,test,style,ci, orbuild. Do not use vague or non-conforming subjects such asupdate,changes,fix stuff, or bare prose. - Breaking changes must use
!after the type or scope, or include aBREAKING CHANGE:footer. Commit messages must remain in English and must never includeCo-Authored-Bylines. - Never use browser-native
alert(),confirm(), orprompt(). Always use custom JS dialogs/modals instead. - When rebuilding daemon config (e.g.
restartDaemonFromConfig()), always useObject.assign({}, lastConfig, overrides)to preserve all existing settings. Never reconstruct config by manually listing fields. - Before adding new code, read docs/guides/MODULE_MAP.md to find the right file. Never add inline logic to
project.jshandleMessage. Keep modules under 500 lines. - Never use
localStoragefor user settings or preferences. All settings must be stored server-side (via WebSocket messages or REST API) so they persist across devices and browsers. - Client modules (
lib/public/modules/): state goes in store.js (zustand-like), WS via ws-ref.js, functions via direct import. Never usevar _ctx = null/initXxx(ctx). See docs/guides/CLIENT_MODULE_DEPS.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 First seen · 17 lines · 525 tokens per session scan A 166861bbb6f5
clay CLAUDE.md is an instructions file published in the GitHub repository chadbyte/clay (390 stars, last pushed 2d ago), licensed MIT. It adds 525 tokens to every session, about $0.0026 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
metabot AGENTS.md
Instructions for xvirobotics/metabot, covering metabot personal edition workspace, core cli, working principles, durable state and public boundary.
metabot CLAUDE.md
Instructions for xvirobotics/metabot: The canonical project instructions are in AGENTS.md. Follow that file for this repository. This compatibility file exists for Claude Code; MetaBot install/update does not deploy or replace workspace instruction files.
Kagura CLAUDE.md
Instructions for Innei/Kagura, covering claude.md, build & run, push & deploy, commit first, then push with lock protection and development workflow.
meridian CLAUDE.md
Claude Code instructions for rynfar/meridian, covering claude.md, what this is, commands, code rules and module boundaries.
myPKA CLAUDE.md
Claude Code instructions for myICOR/myPKA, covering claude.md, first run check (read this before doing anything else), identity (mandatory — applies every session), source of truth and specialist dispatch (claude code specific).
claude-proj-blueprint CLAUDE.md
Claude Code instructions for maduwanthasathsara0-hub/claude-proj-blueprint, covering project, tech stack, architecture, documentation directories and code conventions.