documentation

A documentation workflow for updating the pages affected by a code change and recording follow-up work.

In plain words
What is it for?
It identifies affected pages, sends their updates to a documentation writer, records the change, and checks related backlog items.
Why use it?
It helps prevent public documentation from becoming out of date or missing important changes.

Skill for Claude CodeCodex

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 skills/scolladon/craft/documentation
Any agent
npx skills add scolladon/craft --skill documentation
Clone the repo
git clone --depth 1 https://github.com/scolladon/craft

Made for: Claude Code, Codex.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 848 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.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.00848
Opus 5 $0.00016 $0.00424
Sonnet 5 $0.00006 $0.00170
Haiku 4.5 $0.00003 $0.00085

Measured 2d ago against content hash 7ecc368197d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

documentation 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.

skills/documentation/SKILL.md · 55 lines

How it starts

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

craft:documentation

Preamble (always runs — non-overridable)

  1. Manifest read (lint if standalone). Probe: backlog: declared? (else no backlog work); which doc pages the change actually affects — the affected-page floor is mechanical: (diff ∩ subjects) ∪ probe — the existing judgment probe (public surface, behaviour a page states) UNIONed with every living page whose declared subjects the diff matches (via the intention port's consult; see docs/contributing/specs/intention.md). A coverage gap — a load-bearing changed scope matched by no page's subjects, under intention.covers — escalates via the blocker protocol { unit, reason, ≤3 options } rather than silently passing.

Procedure (default body — a manifest override: replaces everything below)

Runs in parallel with the validation phase's background run.

  1. Pages — only if any are affected: spawn craft:docs-writer with the affected page list + what changed per page, the design doc path as content source, the commit message docs(<slug>): refresh pages, and the context files. Page refresh/create routes through the intention port's record. docs-writer stays update-only — it never creates a new page; a coverage gap that implies a missing page is a human decision, escalated per the Preamble, never auto-created. No affected pages → skip honestly (run record).
  2. Backlog tick — guarded by source (see docs/contributing/specs/backlog.md):
    • source: fileconsult backlog-write action (default always, ADR-127; see docs/contributing/specs/policy.md for surface semantics); then spawn craft:backlog-ticker with the exact entry line and the exact reference suffix. Accept ONLY if the diff touches exactly the expected line(s) — otherwise discard and do the one-line edit yourself.
    • source: customconsult external-send action (default ask, ADR-127; see docs/contributing/specs/policy.md); on proceed, run ref with argv ["complete", id, ...refs]; id/refs are untrusted, passed as discrete arguments (never spliced into a shell string) and id validated against the source's id-form before invoking (see the spec's safe-invocation note). A non-zero exit is a blocker (never a silent tick-skip); idempotency is the custom script's documented contract (see docs/contributing/specs/backlog.md), not framework-asserted.

Read the full file on GitHub · 55 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.

  1. 2d ago First seen · 55 lines · 32 tokens per session scan A 7ecc368197d5

Subscribe to this mod's changes

documentation is a skill published in the GitHub repository scolladon/craft (2 stars, last pushed 14d ago), licensed MIT. It adds 32 tokens to every session and 848 once invoked, about $0.0002 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-31.