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 skills/catlog22/claude-code-workflow/workflow-executenpx skills add catlog22/Claude-Code-Workflow --skill workflow-executegit 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/skills/catlog22/claude-code-workflow/workflow-execute)<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/workflow-execute"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/workflow-execute.svg" alt="Measured on agentmods" 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 | $0.00031 | $0.06302 |
| Opus 5 | $0.00015 | $0.03151 |
| Sonnet 5 | $0.00006 | $0.01260 |
| Haiku 4.5 | $0.00003 | $0.00630 |
Grade A, and why
workflow-execute 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 yesterday.
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 — 626 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Execute
Orchestrates autonomous workflow execution through systematic task discovery, agent coordination, and progress tracking. Executes entire workflow without user interruption (except initial session selection if multiple active sessions exist), providing complete context to agents and ensuring proper flow control execution with comprehensive TodoWrite tracking.
Resume Mode: When called with --resume-session flag, skips discovery phase and directly enters TodoWrite generation and agent execution for the specified session.
Usage
# Interactive mode (with confirmations)
/workflow-execute
/workflow-execute --resume-session="WFS-auth"
# Auto mode (skip confirmations, use defaults)
/workflow-execute --yes
/workflow-execute -y
/workflow-execute -y --resume-session="WFS-auth"
# With auto-commit (commit after each task completion)
/workflow-execute --with-commit
/workflow-execute -y --with-commit
/workflow-execute -y --with-commit --resume-session="WFS-auth"
Auto Mode Defaults
When --yes or -y flag is used:
- Session Selection: Automatically selects the first (most recent) active session
- Completion Choice: Automatically completes session (runs
/workflow:session:complete --yes)
When --with-commit flag is used:
- Auto-Commit: After each agent task completes, commit changes based on summary document
- Commit Principle: Minimal commits - only commit files modified by the completed task
- Commit Message: Generated from task summary with format: "feat/fix/refactor: {task-title} - {summary}"
Flag Parsing:
// ★ 统一 auto mode 检测：-y/--yes 从 $ARGUMENTS 或 ccw 传播
const autoYes = /\b(-y|--yes)\b/.test($ARGUMENTS)
const withCommit = $ARGUMENTS.includes('--with-commit')
Performance Optimization Strategy
Lazy Loading: Task JSONs read on-demand during execution, not upfront. TODO_LIST.md + IMPL_PLAN.md provide metadata for planning.
Loading Strategy:
- TODO_LIST.md: Read in Phase 3 (task metadata, status, dependencies for TodoWrite generation)
- IMPL_PLAN.md: Check existence in Phase 2 (normal mode), parse execution strategy in Phase 4A
- Task JSONs: Lazy loading - read only when task is about to execute (Phase 4B)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 626 lines · 31 tokens per session scan A aecb2fed9c05
workflow-execute is a skill published in the GitHub repository catlog22/Claude-Code-Workflow (2,133 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 6,302 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-09-03.
Other skills, from other repositories
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).
artifact-management
Use for PACEflow artifact fields and formats: task indexes, CHG/HOTFIX lifecycle operations, artifact-writer prompts, approvals, verification, and archive.
tasks
Create or update the live task dashboard (TASKS.md) in Obsidian. Use when the user wants to view or regenerate the task dashboard — 'show my tasks', 'update TASKS.md', 'open task view'. Do NOT use for: the vault portal/map (use moc), capturing new tasks (add them inside project notes directly), or daily briefing (use…
project_management
对项目结构和工作流进行管理.