Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/keepYaoung/artifact-organizernpx agentmods add commands/keepyaoung/artifact-organizer/outprintWrote 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/keepyaoung/artifact-organizer/outprint)<a href="https://agentmods.dev/commands/keepyaoung/artifact-organizer/outprint"><img src="https://agentmods.dev/badge/commands/keepyaoung/artifact-organizer/outprint/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/keepyaoung/artifact-organizer/outprint"><img src="https://agentmods.dev/badge/commands/keepyaoung/artifact-organizer/outprint.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.00046 | $0.01684 |
| Opus 5 | $0.00023 | $0.00842 |
| Sonnet 5 | $0.00009 | $0.00337 |
| Haiku 4.5 | $0.00005 | $0.00168 |
Grade A, and why
outprint 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 8d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 0 — theme + renderer preference (run first, every invocation)
When PREF is empty below, you MUST prompt the user for theme + renderer via AskUserQuestion BEFORE writing the preference file — theme options: notion (warm cream + Notion Blue), linear (dark-native + indigo), vercel (gallery white + Geist), stripe (weight-300 luxury + deep navy), supabase (dark-native + emerald), apple (SF + Apple Blue + true-black dark), tailwind (Inter + slate + indigo-600); renderer options: auto / canvas / page. Use the answer to set THEME and RENDERER. If the user skips or the tool is unavailable, fall back silently to notion + auto. Color mode is not a setting — every output inlines both light and dark; the toggle button + prefers-color-scheme switch them at view time.
PREF=""
for p in ./.artifact-organizer/preference.md ~/.artifact-organizer/preference.md; do
[ -f "$p" ] && { PREF="$p"; break; }
done
if [ -z "$PREF" ]; then
# See the instruction above — populate from AskUserQuestion or fall back.
THEME=notion; RENDERER=auto
mkdir -p ~/.artifact-organizer; PREF=~/.artifact-organizer/preference.md
printf -- '---\ntheme: %s\nrenderer: %s\ncreated_at: %s\n---\n' \
"$THEME" "$RENDERER" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > "$PREF"
fi
THEME=$(awk -F': *' '/^theme:/{print $2; exit}' "$PREF")
RENDERER=$(awk -F': *' '/^renderer:/{print $2; exit}' "$PREF")
[ -z "$THEME" ] && THEME=notion
[ -z "$RENDERER" ] && RENDERER=auto
You are invoking Artifact Organizer's general-purpose renderer. The user asked for:
$ARGUMENTS
Your workflow
- Understand intent. What is the user trying to communicate visually?
- Architecture/flow → Mermaid or ArchitectureGrid
- Comparison → Comparison or DataTable
- Ordered guidance / milestone recap → StepList
- Metrics summary → KPICards, Charts, and DataTable
- Code review → CodeDiff + Callouts
- Essay-style explanation → Page with Sections, Headings, Prose, and embedded components
- Repo / project explainer → start diagram-first with
ArchitectureGrid,FlowChart,Sequence, orMermaid, then useFileTree,FileCard, orAnnotatedCodeas evidence
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.
- 8d ago First seen · 131 lines · 46 tokens per session scan A 658273d2f06c
outprint is a command published in the GitHub repository keepYaoung/artifact-organizer (2 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 1,684 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.
Other commands, from other repositories
demo
Generate a custom SaaS product demo video from a URL, in this Claude Code session (no API key).
cover
Generate a 1600×500 SVG cover banner for a project README in the article-hero pattern.
slides
Generate a Distill-style slide deck on a topic or paper — paper background, system sans, one idea per slide.
watch
Watch a video (URL or local path). Downloads with yt-dlp, extracts frames with ffmpeg, transcribes from captions or local Whisper (no API key), and answers questions about what's in the video.
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.