Borrowing it
Nothing to install: this file belongs to drobins25/craft. 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/drobins25/craft/main/CLAUDE.mdgit clone --depth 1 https://github.com/drobins25/craftWrote 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/drobins25/craft/claude-md)<a href="https://agentmods.dev/instructions/drobins25/craft/claude-md"><img src="https://agentmods.dev/badge/instructions/drobins25/craft/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/drobins25/craft/claude-md"><img src="https://agentmods.dev/badge/instructions/drobins25/craft/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.00753 | $0.00753 |
| Opus 5.5 | $0.00301 | $0.00301 |
| Sonnet 5.5 | $0.00151 | $0.00151 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
craft 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 5d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft
Open-source Claude Code plugin: a development harness.
- README.md - what craft is and how to use it
- DESIGN.md - architecture, file layout, internals
- CONTRIBUTING.md - contribution workflow for craft itself
This file is the operating contract for Claude working in this repo. Routing and live state are injected on every prompt via the UserPromptSubmit hook (the v1|craft-orchestration-index block) - don't duplicate that here.
Conventions
- Commit messages describe what changed for a public audience. Use conventional prefixes:
feat:/fix:/chore:/refactor:/docs:/test:. Translate internal jargon to what the change DOES. Public craft terms (skills, agents, commands, hooks, cycles, stories, backlog, phases) are fine; internal mechanism names need explanation.- Bad:
fix: chain break when content-spark invokes via Skill tool - Good:
fix: prevent skill nesting from breaking control flow back to caller
- Bad:
- Use regular dashes (-) only, never em dashes, in human-facing text (docs, commit messages, changelog, chat). Em dashes are an AI-text tell. Code and code comments are out of scope; never file or fix them.
- Craft runs from the installed plugin copy, not this working tree. Stories here go through
/craft:story-implementlike any other project. A change to craft's own files takes effect at the next reinstall, so a story that changes the implement loop is exercised by the story after it, not by itself. - Bump
.claude-plugin/plugin.jsonversion once per feature or fix that changes a file craft runs (commands, skills, agents, hooks and the scripts they call) - one bump per logical change (a story, an adhoc fix), in that change's final commit. Users only receive new files when this version changes, so such a change bumps even with nothing worth a changelog entry. Changes to tests, CI or contributor tooling alone never bump. Never per chunk; intermediate chunk commits do not bump. CHANGELOG.mdentries are notable-only - features and user-visible fixes get a## <version> - <YYYY-MM-DD>heading with verb-first, user-facing bullets ("Added...", "Fixed...", "Changed...", "Improved..."). Internal changes to files craft runs (refactors, prompt rewording) bump the version with no entry, and no entry is ever about the repo itself (changelog edits, doc restructures, contributor tooling). Same audience rule as commit messages.check-doc-drift.shblocks a changelog that's ahead of plugin.json, and blocks pushing afeat:commit with no changelog change.- Write every bullet for a craft user, not for us. The test: no internal mechanism names (CDN hosts, metadata fields, gate names, file paths), lead with what the user gets, and say what it feels like to use ("icons now arrive in seconds instead of minutes"), not how it works. The
## 1.99.54entry is the exemplar - match its register.
- Write every bullet for a craft user, not for us. The test: no internal mechanism names (CDN hosts, metadata fields, gate names, file paths), lead with what the user gets, and say what it feels like to use ("icons now arrive in seconds instead of minutes"), not how it works. The
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.
- 5d ago Changed · +87 tokens per session 4ee43590f98c
- 19d ago Changed · -4 lines · -81 tokens per session 91f57d8c9a0a
- 1mo ago Changed · +13 tokens per session dc7494da4cc7
- 1mo ago First seen · 36 lines · 734 tokens per session scan A dc02eb798c06
craft CLAUDE.md is an instructions file published in the GitHub repository drobins25/craft (70 stars, last pushed today), licensed MIT. It adds 753 tokens to every session, about $0.0030 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-30.
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.
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.
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).