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 commands/theclaymethod/artifacture/generate-postergit clone --depth 1 https://github.com/theclaymethod/artifactureWhat 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.00017 | $0.01123 |
| Opus 5 | $0.00009 | $0.00562 |
| Sonnet 5 | $0.00003 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
generate-poster 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load the visual-explainer skill, then generate a fixed-canvas poster for: $@
Authoring contract. Prefer React source. For posters that should use shared visual-explainer components or point-and-click annotation review, write a .tsx source that imports from visual-explainer-mdx/components.tsx, then export generated standalone HTML with:
npm run ve:export -- <poster.tsx> --out ~/.agent/diagrams/<name>.poster.html
Capture the verified generated page as the PNG artifact with browser screenshot tooling. If the poster specifically needs poster-ai's fixed-canvas rasterizer, keep the editable source as TSX and run the poster build / poster export commands below. Do not fall back to hand-written HTML; if both generated React HTML and poster-ai are blocked, stop and report the blocker.
Clarify. This is a Tier 0 (high-cost) command per ./references/clarify.md. Always ask via AskUserQuestion before generating, at minimum: canvas size (1600×1000 landscape / 1200×1500 portrait / 1200×628 social / 1080×1080 square), focal element (stat / headline / diagram / photo), and aesthetic. Bypass only on explicit --no-ask.
Read ./references/poster.md and ./templates/mono-industrial-poster.tsx before generating. Poster output uses poster-ai (CLI binary: poster) to turn a single TSX file into a self-contained HTML poster and a rasterized PNG. It is not a replacement for the primary scrollable HTML flow — it is the right output when the content is intrinsically a fixed-canvas graphic: a shareable summary, a dashboard, an infographic, or a poster for print/social.
Before generating:
- Check availability:
which posteronly if using the poster-ai path. If missing, use the generated React HTML + browser screenshot path above. - Pick a canvas size based on intent:
- Architecture / landscape poster:
w-[1600px] h-[1000px] - Portrait editorial:
w-[1200px] h-[1500px] - Social card (Twitter/LinkedIn):
w-[1200px] h-[628px] - Square (Slack, Instagram):
w-[1080px] h-[1080px]
- Architecture / landscape poster:
- Commit to OA Design by default: clean white plate, quiet grey stage, one ink, one restrained blue accent, Inter Tight at 500 or below, continuous-curvature surfaces, and no grid background. Read
./references/oa-design.md. Usemono-industrial-poster.tsxonly as a mechanical poster-ai scaffold until it is replaced; do not inherit its visual tokens. Use a named alternative only if the user requests one.
Authoring:
- The root of the component MUST be a single element (not a Fragment). Poster measures one element for the canvas.
- Load Google Fonts via a
<link>inside the root element. Geist Pixel Square is not on Google Fonts — load it via an inline<style>@font-faceblock from jsDelivr. Seetemplates/mono-industrial-poster.tsxfor the pattern. - Avoid Mermaid — poster's rasterizer doesn't wait long enough for Mermaid's async render. Use custom SVG, Recharts, or a pre-rendered Mermaid SVG as an
<img>. - Exactly one moment of surprise per poster (Geist Pixel display number, oversized word, broken-grid element).
Workflow:
- Draft the TSX at
~/.agent/diagrams/<name>.poster.tsxfollowing the Mono-Industrial pattern. - Run
/unslopon all prose copy (headlines, descriptions, body) before writing into the TSX. See SKILL.md § 4. - Build:
poster build ~/.agent/diagrams/<name>.poster.tsx -o ~/.agent/diagrams/<name>.poster.html - Export PNG:
poster export ~/.agent/diagrams/<name>.poster.tsx -o ~/.agent/diagrams/<name>.poster.png - Verify in the browser (see SKILL.md § 6): open the HTML, confirm canvas renders correctly, hierarchy legible, status colors only on values.
- Canvas-fit loop (mandatory — see
./references/poster.md→ "Canvas-fit verification loop"). Load the exported PNG and inspect it. Posters clip silently at the canvas edge, and the live HTML lies about this — only the PNG shows the real cropped result. If text is clipped, elements are cut by the boundary, empty space suggests a collapsed grid, the hierarchy no longer reads, or the moment of surprise got shrunk to fit, rework the TSX and re-export. Bounded at 3 attempts; if still broken, stop and report. - Tell the user both file paths (HTML for live viewing with the export toolbar, PNG for sharing).
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.
- 2d ago First seen · 46 lines · 17 tokens per session scan A e9b2824ac562
generate-poster is a command published in the GitHub repository theclaymethod/artifacture (2 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 1,123 once invoked, about $0.0001 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.
Other commands, from other repositories
editor
You are my personal writing editor for MDX/Markdown content. Improve clarity, flow, grammar, and style while preserving the author's voice, meaning, and factual details. Infer the content type and appropriate tone from the context.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.