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/khaledsaeed18/dotclaude/claude-mdgit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/claude-md)<a href="https://agentmods.dev/instructions/khaledsaeed18/dotclaude/claude-md"><img src="https://agentmods.dev/badge/instructions/khaledsaeed18/dotclaude/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.00935 | $0.00935 |
| Opus 5 | $0.00467 | $0.00467 |
| Sonnet 5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
dotclaude 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotclaude
Personal Claude Code registry: skills, agents, commands, and hooks, distributed via the shadcn registry and a Claude Code plugin marketplace. Full contributor guide: CONTRIBUTING.md.
The one rule: source vs generated
Every item lives at <type>/<category>/<name>/<MANIFEST> (SKILL.md, AGENT.md, COMMAND.md, or HOOK.md). Everything else is derived by pnpm gen:
- each item's
registry.jsonand the rootregistry.json - the README catalog, badges, and plugins table (between
<!-- ... -->markers) - everything under
.claude-plugin/(marketplace + per-plugin trees)
Never hand-edit generated files. Edit the source manifest, run pnpm gen, and commit the regenerated output. pnpm gen:check fails CI when anything is stale.
One thing deliberately sits outside that rule: .agents/skills/improve/, surfaced to this repo's own sessions through the .claude/skills/improve symlink. It is tooling for working on the registry, not an item in it — so it is invisible to gen and validate, follows none of the item conventions, and ships to nobody. Anything under skills/, agents/, commands/, or hooks/ is a registry item; .agents/ is not.
Verification gate
Run before considering any change done (same as CI):
pnpm typecheck && pnpm lint && pnpm test && pnpm gen:check && pnpm validate
pnpm coverage reports how much of hooks/ and scripts/ the suite actually
executes, and fails below 90%. It exists because the suite is black-box — hooks
run as child processes — so ordinary coverage tooling instruments only the
runner and reports a confident, wrong 0%. This collects V8 coverage from the
children and merges it. Use it to find untested branches, not to chase 100%:
some branches are platform-specific and unreachable on a given OS.
pnpm smoke is the slower end-to-end check CI also runs, kept out of the line above because it drives the real Claude Code CLI: it installs every generated plugin into a throwaway config dir, diffs the installed tree against the generated one, and runs each bundled hook script from its installed path (including that the deny rules still block). Run it after touching gen.ts's plugin logic or any hook script. It needs no auth or network beyond resolving the CLI, and leaves nothing behind.
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 · 55 lines · 935 tokens per session scan A c4f3bbb73c6e
dotclaude CLAUDE.md is an instructions file published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 3d ago), licensed MIT. It adds 935 tokens to every session, about $0.0047 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
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.
mcp-execution mcp-wasm-runtime.instructions.md
Instructions for bug-ops/mcp-execution, covering copilot instructions: mcp-wasm-runtime, security - critical, security principles, security configuration and host function safety.
skillsync-mcp CLAUDE.md
Instructions for adityasugandhi/skillsync-mcp, covering claude.md, project overview, development commands, architecture and key files.
truthmark CLAUDE.md
Claude Code instructions for merlinhu1/truthmark, covering authority, documentation scope, product boundary, rules and instruction surface boundary.