Borrowing it
Nothing to install: this file belongs to qwerfunch/cladding. 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/qwerfunch/cladding/main/CLAUDE.mdgit clone --depth 1 https://github.com/qwerfunch/claddingWrote 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/qwerfunch/cladding/claude-md)<a href="https://agentmods.dev/instructions/qwerfunch/cladding/claude-md"><img src="https://agentmods.dev/badge/instructions/qwerfunch/cladding/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/qwerfunch/cladding/claude-md"><img src="https://agentmods.dev/badge/instructions/qwerfunch/cladding/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.02374 | $0.02374 |
| Opus 5.5 | $0.00950 | $0.00950 |
| Sonnet 5.5 | $0.00475 | $0.00475 |
| Haiku 4.5 | $0.00237 | $0.00237 |
Grade A, and why
cladding 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 1mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintainer guide for AI-assisted work on cladding
This file is read by Claude Code (and any other AI assistant with project-instructions support) when working inside the cladding repo. It captures invariants that aren't visible from a clean git clone — i.e. things a human-or-AI maintainer must respect that aren't enforced by tests or detectors alone.
External cladding users (people running cladding on their own project) read README.md + docs/spec-ids-multi-dev.md instead.
Spec authoring — always hash, never F-NNN
When adding a new spec entry to spec/features/ or spec/scenarios/:
- DO NOT create
spec/features/F-NNN.yaml(the legacy sequential format) by hand. - DO use the hash-based model:
- Filename:
<slug>-<hash8>.yaml(e.g.auth-bypass-c4d108e9.yaml) - Inside the yaml:
id: F-<hash8>plusslug: <slug> - The hash is an 8-character hex string since 0.6.0 (legacy 6-char ids stay valid). Generate with:
node -e "console.log('F-' + require('node:crypto').randomBytes(4).toString('hex'))"
- Filename:
This rule exists because v0.3.9 introduced the multi-developer-safe hash model and external users get hash-based IDs whenever they invoke clad_create_feature via their host AI. Cladding's own spec must dogfood the same model — otherwise the reference implementation drifts from what the standard recommends.
Legacy F-001 ~ F-083 files (authored before v0.3.9) stay sequential — they're stable identifiers in audit logs and historical references. Do not migrate them.
Files F-082 ~ F-090 were the drift period (authored after v0.3.9 but bypassing the hash model). v0.3.16 migrated them via scripts/migrate-dogfood-v0.3.16.mjs.
Version bumps — use the script
Don't hand-edit version strings. There are eleven sites (incl. .claude-plugin/marketplace.json, the marketplace catalog the Claude Code host reads to detect "update available"); missing one breaks HARNESS_INTEGRITY (which now also guards the marketplace catalog version). Run:
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.
- 1mo ago Changed · +2 lines · +39 tokens per session e4fbbaafe0f4
- 1mo ago First seen · 117 lines · 2,335 tokens per session scan A 9f2fa4edd5c6
cladding CLAUDE.md is an instructions file published in the GitHub repository qwerfunch/cladding (16 stars, last pushed 1mo ago), licensed MIT. It adds 2,374 tokens to every session, about $0.0095 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.
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.