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 skills/qwerfunch/cladding/syncnpx skills add qwerfunch/cladding --skill syncgit 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.00103 | $0.00461 |
| Opus 5 | $0.00051 | $0.00230 |
| Sonnet 5 | $0.00021 | $0.00092 |
| Haiku 4.5 | $0.00010 | $0.00046 |
Grade A, and why
sync 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.
What it actually says
Cladding sync
Run clad sync from the project root. The command:
- Loads
spec.yaml(or its sharded form underspec/features/*.yaml). - Validates against
src/spec/schema.json(JSONSchema). - Reports the feature count and any validation failures.
- Exits non-zero when the spec is invalid so CI can gate on it.
Spec must be valid before clad check, clad run, or any stage runner produces meaningful output. If sync fails, fix the reported issues first.
clad sync
When you actually need it (don't reflex-sync)
You rarely need to run this MANUALLY — and a reflexive "just-in-case" sync after every
operation is wasted work (in an A/B measurement, 28 of 30 manual clad sync calls found
nothing to fix). The inventory + validation are already maintained for you:
clad_create_featureauto-syncs the inventory after each feature it writes (and rejects a malformed AC at creation), so you don't need to sync after creating features.clad check/clad donevalidate the spec themselves (drift stage), so you don't need to pre-sync before them — a real drift surfaces in that gate anyway.
Run clad sync only when you have hand-edited a shard file directly (Edit/Write on
spec/features/*.yaml or spec.yaml), to refresh the inventory and re-validate that edit.
Prefer clad_create_feature over hand-editing in the first place — then even this is unneeded.
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 · 34 lines · 103 tokens per session scan A 775c0f990a52
sync is a skill published in the GitHub repository qwerfunch/cladding (14 stars, last pushed 3d ago), licensed MIT. It adds 103 tokens to every session and 461 once invoked, about $0.0005 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 skills, from other repositories
map-plan
ARCHITECT phase - decompose complex tasks into atomic subtasks with research, spec, and branch-scoped plan artifacts under .map.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.
map-debug
Structured MAP debugging via task-decomposer, actor, and monitor agents. Use when reproducing a bug, isolating a regression, or diagnosing an error with specialized agents — including failing or flaky tests (pytest AssertionError), crashes and segmentation faults, memory-corruption or memory errors in native/C…
map-learn
Capture reusable lessons after a completed MAP workflow. Use when a MAP run has finished and you want rules written to .claude/rules/learned/ from a workflow summary or handoff. Do NOT use during active implementation.
map-efficient
State-machine MAP execution workflow for Codex. Use when implementing an approved MAP plan end to end, resuming from branch MAP taskplan or stepstate.json artifacts, or running non-trivial multi-subtask work. Use map-fast for tiny one-shot edits.
map-task
Execute a single subtask from an existing MAP plan via Actor and Monitor. Use when map-plan has decomposed work and you want fine-grained control over one subtask. Do NOT use without an existing plan; run map-plan first.