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/catlog22/Claude-Code-WorkflowWrote 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/catlog22/claude-code-workflow/reference-page-generator)<a href="https://agentmods.dev/commands/catlog22/claude-code-workflow/reference-page-generator"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/reference-page-generator/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/catlog22/claude-code-workflow/reference-page-generator"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/reference-page-generator.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.00020 | $0.02978 |
| Opus 5.5 | $0.00008 | $0.01191 |
| Sonnet 5.5 | $0.00004 | $0.00596 |
| Haiku 4.5 | $0.00002 | $0.00298 |
Grade A, and why
workflow:ui-design:reference-page-generator 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.
How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Design: Reference Page Generator
Overview
Converts design run extraction results into shareable reference package with:
- Interactive multi-component preview (preview.html + preview.css)
- Component layout templates (layout-templates.json)
Role: Takes existing design run (from import-from-code or other extraction commands) and generates preview pages for easy reference.
Usage
Command Syntax
/workflow:ui-design:reference-page-generator [FLAGS]
# Flags
--design-run <path> Design run directory path (required)
--package-name <name> Package name for reference (required)
--output-dir <path> Output directory (default: .workflow/reference_style)
Execution Process
Input Parsing:
├─ Parse flags: --design-run, --package-name, --output-dir
└─ Validation:
├─ --design-run and --package-name REQUIRED
└─ Package name format: lowercase, alphanumeric, hyphens only
Phase 0: Setup & Validation
├─ Step 1: Validate required parameters
├─ Step 2: Validate package name format
├─ Step 3: Validate design run exists
├─ Step 4: Check required extraction files (design-tokens.json, layout-templates.json)
└─ Step 5: Setup output directory
Phase 1: Prepare Component Data
├─ Step 1: Copy layout templates
├─ Step 2: Copy design tokens
└─ Step 3: Copy animation tokens (optional)
Phase 2: Preview Generation (Agent)
└─ Generate preview.html + preview.css via ui-design-agent
Phase 0: Setup & Validation
Purpose: Validate inputs, prepare output directory
Operations:
# 1. Validate required parameters
if [ -z "$design_run" ] || [ -z "$package_name" ]; then
echo "ERROR: --design-run and --package-name are required"
echo "USAGE: /workflow:ui-design:reference-page-generator --design-run <path> --package-name <name>"
exit 1
fi
# 2. Validate package name format (lowercase, alphanumeric, hyphens only)
if ! [[ "$package_name" =~ ^[a-z0-9][a-z0-9-]*$ ]]; then
echo "ERROR: Invalid package name. Use lowercase, alphanumeric, and hyphens only."
echo "EXAMPLE: main-app-style-v1"
exit 1
fi
# 3. Validate design run exists
if [ ! -d "$design_run" ]; then
echo "ERROR: Design run not found: $design_run"
echo "HINT: Run '/workflow:ui-design:import-from-code' first to create design run"
exit 1
fi
# 4. Check required extraction files exist
required_files=(
"$design_run/style-extraction/style-1/design-tokens.json"
"$design_run/layout-extraction/layout-templates.json"
)
for file in "${required_files[@]}"; do
if [ ! -f "$file" ]; then
echo "ERROR: Required file not found: $file"
echo "HINT: Ensure design run has style and layout extraction results"
exit 1
fi
done
# 5. Setup output directory and validate
output_dir="${output_dir:-.workflow/reference_style}"
package_dir="${output_dir}/${package_name}"
# Check if package directory exists and is not empty
if [ -d "$package_dir" ] && [ "$(ls -A $package_dir 2>/dev/null)" ]; then
# Directory exists - check if it's a valid package or just a directory
if [ -f "$package_dir/metadata.json" ]; then
# Valid package - safe to overwrite
existing_version=$(jq -r '.version // "unknown"' "$package_dir/metadata.json" 2>/dev/null || echo "unknown")
echo "INFO: Overwriting existing package '$package_name' (version: $existing_version)"
else
# Directory exists but not a valid package
echo "ERROR: Directory '$package_dir' exists but is not a valid package"
echo "Use a different package name or remove the directory manually"
exit 1
fi
fi
mkdir -p "$package_dir"
echo "[Phase 0] Setup Complete"
echo " Design Run: $design_run"
echo " Package: $package_name"
echo " Output: $package_dir"
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 First seen · 357 lines · 20 tokens per session scan A 7e37b7369535
workflow:ui-design:reference-page-generator is a command published in the GitHub repository catlog22/Claude-Code-Workflow (2,125 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 2,978 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-09-03.
Other commands, from other repositories
multi-frontend
Run a frontend-focused multi-model workflow for components, layouts, animation, and UI polish.
create-excalidraw-diagram
description: "Create system architecture or technical diagram (Excalidraw) (Use any time you need a diagram)".
verify-claim
Walk a claim through the SIFT method (Stop, Investigate, Find better coverage, Trace).
my_brand
Interactive brand identity creation with archetypes, colors, typography, and voice guidelines. Use when user mentions "brand", "colors", "typography", "brand.md", "design system", or "visual identity".
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.