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/explore-auto)<a href="https://agentmods.dev/commands/catlog22/claude-code-workflow/explore-auto"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/explore-auto/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/explore-auto"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/explore-auto.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.00000 | $0.07384 |
| Opus 5.5 | $0.00000 | $0.02954 |
| Sonnet 5.5 | $0.00000 | $0.01477 |
| Haiku 4.5 | $0.00000 | $0.00738 |
Grade C, and why
explore-auto scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Bash(rm -rf "{base_path}/style-extraction" "{base_path}/animation-extraction" "{base_path}/layout-extraction" 2>/dev/null) How it starts
The opening of the file, as written. The whole thing — 679 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Design Auto Workflow Command
Overview & Execution Model
Fully autonomous orchestrator: Executes all design phases sequentially from style extraction to design integration, with optional batch planning.
Unified Target System: Generates style_variants × layout_variants × targets prototypes, where targets can be:
- Pages (full-page layouts): home, dashboard, settings, etc.
- Components (isolated UI elements): navbar, card, hero, form, etc.
- Mixed: Can combine both in a single workflow
Autonomous Flow (⚠️ CONTINUOUS EXECUTION - DO NOT STOP):
- User triggers:
/workflow:ui-design:explore-auto [params] - Phase 5: Target confirmation → User confirms → IMMEDIATELY triggers Phase 7
- Phase 7 (style-extract) → Attach tasks → Execute → Collapse → Auto-continues to Phase 8
- Phase 8 (animation-extract, conditional):
- IF should_extract_animation: Attach tasks → Execute → Collapse → Auto-continues to Phase 9
- ELSE: Skip (use code import) → Auto-continues to Phase 9
- Phase 9 (layout-extract) → Attach tasks → Execute → Collapse → Auto-continues to Phase 10
- Phase 10 (ui-assembly) → Attach tasks → Execute → Collapse → Workflow complete
Phase Transition Mechanism:
- Phase 5 (User Interaction): User confirms targets → IMMEDIATELY executes Phase 7
- Phase 7-10 (Autonomous): Skill execute ATTACHES tasks to current workflow
- Task Execution: Orchestrator EXECUTES these attached tasks itself
- Task Collapse: After tasks complete, collapse them into phase summary
- Phase Transition: Automatically execute next phase after collapsing
- No additional user interaction after Phase 5 confirmation
Auto-Continue Mechanism: TodoWrite tracks phase status with dynamic task attachment/collapse. After executing all attached tasks, you MUST immediately collapse them, restore phase summary, and execute the next phase. No user intervention required. The workflow is NOT complete until Phase 10 (UI assembly) finishes.
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 · 679 lines · 0 tokens per session scan C 19efc45fa068
explore-auto is a command published in the GitHub repository catlog22/Claude-Code-Workflow (2,125 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,384 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.