A command workflow for initializing or adopting Cladding in a project. It can prepare setup from an idea, a planning document, or an existing codebase, then waits for approval before applying changes.

It helps initialize a new Cladding project, adopt Cladding in an existing codebase, or refresh an existing setup when explicitly requested.

It prevents accidental setup and gives the user a reviewable list of planned changes before the project is modified.

init — Command by qwerfunch

Install

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.

agentmods

npx agentmods add commands/qwerfunch/cladding/init

Clone the repo

git clone --depth 1 https://github.com/qwerfunch/cladding

Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 739 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00052	$0.00739
Opus 5	$0.00026	$0.00369
Sonnet 5	$0.00010	$0.00148
Haiku 4.5	$0.00005	$0.00074

Measured yesterday against content hash cc23bc61906c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

init 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 yesterday.

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.

plugins/claude-code/commands/init.md · 31 lines

How it starts

The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cladding init

Use this workflow only when the user explicitly asks to initialize, adopt, or refresh Cladding. Opening a repository alone is not consent to initialize it.

Required host workflow

If the current user message itself matches APPLY CLADDING XXXXXX, do not call prepare or stage again. Call clad_init once and copy the entire user message, including the APPLY CLADDING prefix, into confirmation.

If a greenfield request has no project intent, ask for one short description.
Call clad_prepare_init with exactly one starting mode:
- idea with the user's description.
- document with a project-relative planning-document path.
- existing for an existing codebase; include an optional adoption goal.
Read the returned prompt and observations. Draft the structured object required by clad_init using the current host model, then call clad_stage_init with the preparation token and that draft. Staging validates the draft and stores only ignored runtime state under .cladding/host/; it does not modify authored project files.
Show plannedChanges, the staged confirmationQuestion, and its one-time approvalChallenge to the user, then stop and wait for a separate reply. The original initialization request is not confirmation.
Only when the user's separate reply exactly matches approvalChallenge, call clad_init with the entire reply verbatim as confirmation—never strip the APPLY CLADDING prefix. Include the draft and token when the host retained them; process-per-turn hosts may omit both because Cladding resolves the exact staged draft from its short-lived machine-local cache. Questions, paraphrases, and generic acknowledgements are not approval.
If nextQuestion is present, show it verbatim and end the assistant turn immediately. Never answer it, infer an answer, or call either clarify tool during the initialization-approval turn. Continue with the Cladding clarify workflow only after a new user message supplies the answer. If no question remains, report that onboarding is complete and that the next step is to author the first feature's spec — its acceptance criteria and the files it will cover — before writing any code; the feature cycle starts there, not with scaffolding.

Read the full file on GitHub · 31 lines

Changes

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.

yesterday First seen · 31 lines · 52 tokens per session scan A cc23bc61906c

Subscribe to this mod's changes

init is a command published in the GitHub repository qwerfunch/cladding (14 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 739 once invoked, about $0.0003 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.

Documents Planning Productivity ai-coding claude-code claude-code-plugin codex-cli cursor-ide drift-detection

init

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Cladding init

Required host workflow

What this file has done since we first saw it

Other commands, from other repositories

iterate

init

task

mode

issue

fix