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/generate-web-diagram)<a href="https://agentmods.dev/commands/theclaymethod/artifacture/generate-web-diagram"><img src="https://agentmods.dev/badge/commands/theclaymethod/artifacture/generate-web-diagram/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/generate-web-diagram"><img src="https://agentmods.dev/badge/commands/theclaymethod/artifacture/generate-web-diagram.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.00007 | $0.00348 |
| Opus 5.5 | $0.00003 | $0.00139 |
| Sonnet 5.5 | $0.00001 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
generate-web-diagram 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 15d 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 SKILL.md and cards/web-diagram.md, then explain: $@
For comparisons or tabular data, use cards/comparison-table.md instead.
- Inspect the supplied sources. State the question the diagram answers and identify the nodes, relationships, and boundaries needed to answer it.
- Use
DiagramCanvasfor its supported layouts. Let content determine node size; split dense graphs into overview and detail. Read the card's conditional references for specialized types or custom SVG. - Keep MDX/TSX or Archify typed JSON as editable source, export through its route, and complete
references/verification.mdthrough the finalizer. Save to~/.agent/diagrams/<slug>.htmlwith its editable source alongside it.
Use the default ISO preset unless the user names another. Labels, connectors, and supporting prose must explain the system; omit decorative headings, metrics, status, and legends.
Independent sections
When three or more substantial sections can be built independently, use available parallel agents unless --no-parallel was passed. Give each worker its source evidence, content scope, and shared component/preset contract. Keep source ownership separate; integrate in the parent MDX/TSX artifact.
Raw HTML fragment fallback uses references/section-contract.md. Its specialist mappings remain ve-hero-builder, ve-diagram-builder, and ve-table-builder; dashboard and prose use a generic worker. Validate returned fragments and allow at most one retry per section before completing it locally.
Do not split a single diagram across workers. Build summaries after the evidence they summarize is available.
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.
- 15d ago Changed 877acfec377a
- 16d ago Changed 3bc38f45652d
- 1mo ago Changed · -35 lines · -5 tokens per session 0a67e941dd43
- 1mo ago First seen · 55 lines · 12 tokens per session scan A 6fdf03bc59d2
generate-web-diagram is a command published in the GitHub repository theclaymethod/artifacture (3 stars, last pushed 5d ago), licensed MIT. It adds 7 tokens to every session and 348 once invoked, about $0.0000 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
learn
Force claude-smart to extract learnings from this session now.
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
init
Install the formatters this repository needs, with every command visible before it runs.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.