Borrowing it
Nothing to install: this file belongs to KhaledSaeed18/dotclaude. 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/KhaledSaeed18/dotclaude/main/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/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/khaledsaeed18/dotclaude/claude-md"><img src="https://agentmods.dev/badge/instructions/khaledsaeed18/dotclaude/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.01471 | $0.01471 |
| Opus 5.5 | $0.00588 | $0.00588 |
| Sonnet 5.5 | $0.00294 | $0.00294 |
| Haiku 4.5 | $0.00147 | $0.00147 |
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 25d 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 — 62 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) site/data.json, the one file the catalog site reads- one crawlable page per item and per plugin under
site/<type>/<name>/andsite/plugins/<name>/(plus each item'sindex.md),site/sitemap.xmlandsite/llms-full.txt, all fromscripts/site-pages.ts NOTICE.md, the attributions collected from every manifest's## Attributionsection
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.
The catalog site lives in site/: static HTML, CSS, and JS with no build step and no dependencies, deployed to dotclaude.khaledsaeed.tech by .github/workflows/pages.yml on every push to main that touches site/. Its only data source is the generated site/data.json, so the site never needs editing when items change; index.html, styles.css, and app.js are hand-written and Biome-linted like the rest of the repo. Three marked regions inside index.html (meta, rows and jsonld) and site/llms.txt are generated too, so crawlers that do not run JavaScript still see the full catalog. The per-item and per-plugin pages are the canonical URLs for search and answer engines (own title, description, Open Graph, BreadcrumbList and SoftwareSourceCode JSON-LD, the rendered manifest); the home page's rows link to them and the app opens its panel on a plain click. Preview locally with any static server, e.g. python3 -m http.server 4173 --directory site.
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.
- 25d ago Changed · +1 lines · +120 tokens per session bfee37d13746
- 1mo ago Changed · +6 lines · +416 tokens per session d4450c867bfe
- 2mo 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 1,471 tokens to every session, about $0.0059 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.