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.
git clone --depth 1 https://github.com/theclaymethod/artifactureWrote 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/commands/theclaymethod/artifacture/explain-diff)<a href="https://agentmods.dev/commands/theclaymethod/artifacture/explain-diff"><img src="https://agentmods.dev/badge/commands/theclaymethod/artifacture/explain-diff/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/commands/theclaymethod/artifacture/explain-diff"><img src="https://agentmods.dev/badge/commands/theclaymethod/artifacture/explain-diff.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.00015 | $0.00571 |
| Opus 5.5 | $0.00006 | $0.00228 |
| Sonnet 5.5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
explain-diff 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.
What it actually says
Load the visual-explainer skill, then generate an explain-diff page as a self-contained HTML artifact.
Credit: this mode adapts Geoffrey Litt's "explain-diff" gist: https://gist.github.com/geoffreylitt/a29df1b5f9865506e8952488eac3d524
Which diff command to use. Use /explain-diff when the reader needs a teaching walkthrough; use /diff-review when the reader needs reviewer-risk findings.
Arguments. $1 may be a diff range, PR number, branch, commit, or file path. If omitted, use staged changes when present; otherwise default to HEAD~1..HEAD.
Scope detection.
- PR number (
#42):gh pr diff 42 - Range (
abc..def):git diff abc..def - Branch:
git diff <branch>...HEAD - Commit:
git show <commit> - No argument:
git diff --staged; if empty,git diff HEAD~1..HEAD
Data gathering.
- Read the diff and
git diff --stat/--name-statusfor scope. - Read surrounding code before and after each meaningful hunk. Do not explain a line without knowing the function/module contract around it.
- Identify the audience-facing background: what system this code belongs to, what invariant existed before, and what behavior the diff changes.
- Build a fact sheet with cited file paths, function names, and claims before authoring.
Authoring contract.
Read cards/explain-diff.md. Write MDX, no top-level tabs. Use a long page that establishes the old behavior, explains the change, shows the relevant code, and checks understanding. Name sections for their content; add a table of contents when the length warrants it. Use DiffBlock, CodeBlock, and Quiz; use DiagramCanvas/MermaidBlock for 1-2 reusable diagram families and reuse them across sections with example data.
Explain the changed behavior through a concrete input and outcome. Define unfamiliar terms where they enter the explanation; remove sentences that repeat the code or heading. Use the optional companion route only when requested.
Output path:
mkdir -p ~/.agent/diagrams
npm run ve:export -- <source.mdx> --out ~/.agent/diagrams/$(date +%F)-explain-<slug>.html
Then complete references/verification.md on the exported HTML and report the artifact path, report JSON, screenshots directory, and any remaining uncertainty.
$@
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 e103d0cfa500
- 1mo ago First seen · 40 lines · 15 tokens per session scan A 22b287c822c6
explain-diff is a command published in the GitHub repository theclaymethod/artifacture (3 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 571 once invoked, about $0.0001 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-31.
Other commands, from other repositories
design-tutorial
Interactive guided tour of Naksha — learn commands through real exercises, discover workflows, and get oriented in under 10 minutes.
naksha-help
Quick-reference for any Naksha command — browse by category or look up a specific command.
ccc-compound
Capture the patterns, corrections and decisions from the work just done into tasks/lessons.md, or review and prune existing lessons. Use after finishing a task or when the user says compound, lessons or retro.
code-explainer
Use when a designer needs to understand code that already works. What a file does, what a line means, which parts are safe to change. Plain language with Figma analogies, no developer jargon.
practice-exercise
Generate personalized coding exercises based on your codebase patterns and skill level. Includes progressive hints, solution review, and hands-on learning challenges.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.