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/qwerfunch/cladding/claude-mdgit clone --depth 1 https://github.com/qwerfunch/claddingWhat 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.02335 | $0.02335 |
| Opus 5 | $0.01167 | $0.01167 |
| Sonnet 5 | $0.00467 | $0.00467 |
| Haiku 4.5 | $0.00233 | $0.00233 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 117 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>-<hash>.yaml(e.g.auth-bypass-c4d108e9.yaml) - Inside the yaml:
id: F-<hash>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.
- 2d 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 (14 stars, last pushed 4d ago), licensed MIT. It adds 2,335 tokens to every session, about $0.0117 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
parallel-code CLAUDE.md
Instructions for johannesjo/parallel-code, covering parallel code, stack, commands, project structure and conventions.
map-framework CLAUDE.md
Instructions for azalio/map-framework, covering map framework (mapify-cli) — agent instructions, what this repo is, critical invariant: template single-source render, skill catalog invariant and how to work in this repo.
vibe-code-stack-for-ceos AGENTS.md
Instructions for NoahDuongMaster/vibe-code-stack-for-ceos, covering agents.md — vibe code stack for ceos, monorepo map, commands, definition of done and architecture rules.
ai-driven-development AGENTS.md
Instructions for CodeAlive-AI/ai-driven-development, covering ai-driven development — development guide, git publishing defaults, when to create tags and releases, requires a new tag/release and does not require a new tag/release.
agents AGENTS.md
Instructions for scarletkc/agents, covering agent guidelines, environment, engineering principles, code style and testing.
codex-command-center AGENTS.md
Instructions for sevensir888/codex-command-center, a project described as: A local desktop control center for organizing Codex projects, engineering tasks, sessions, Git changes, Skills, and MCP configuration.