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 skills add catlog22/Claude-Code-Workflow --skill wf-composergit 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/wf-composer)<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/wf-composer"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/wf-composer/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/skills/catlog22/claude-code-workflow/wf-composer"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/wf-composer.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.00055 | $0.01188 |
| Opus 5.5 | $0.00022 | $0.00475 |
| Sonnet 5.5 | $0.00011 | $0.00238 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
wf-composer 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Design
Parse user's semantic workflow description → decompose into nodes → map to executors → auto-inject checkpoints → confirm pipeline → save as reusable workflow-template.json.
Architecture
User describes workflow in natural language
-> Phase 1: Parse — extract intent steps + variables
-> Phase 2: Resolve — map each step to executor (skill/cli/agent/command)
-> Phase 3: Enrich — inject checkpoint nodes, set DAG edges
-> Phase 4: Confirm — visualize pipeline, user approval/edit
-> Phase 5: Persist — save .workflow/templates/<name>.json
Shared Constants
| Constant | Value |
|---|---|
| Session prefix | WFD |
| Template dir | .workflow/templates/ |
| Template ID format | wft-<slug>-<date> |
| Node ID format | N-<seq> (e.g. N-001), CP-<seq> for checkpoints |
| Max nodes | 20 |
Entry Router
Parse $ARGUMENTS.
| Detection | Condition | Handler |
|---|---|---|
| Resume design | --resume flag or existing WFD session |
-> Phase 0: Resume |
| Edit template | --edit <template-id> flag |
-> Phase 0: Load + Edit |
| New design | Default | -> Phase 1: Parse |
Phase 0: Resume / Edit (optional)
Resume design session:
- Scan
.workflow/templates/design-drafts/WFD-*.jsonfor in-progress designs - Multiple found → AskUserQuestion for selection
- Load draft → skip to last incomplete phase
Edit existing template:
- Load template from
--editpath - Show current pipeline visualization
- AskUserQuestion: which nodes to modify/add/remove
- Re-enter at Phase 3 (Enrich) with edits applied
Phase 1: Parse
Read phases/01-parse.md and execute.
Objective: Extract structured semantic steps + context variables from natural language.
Success: design-session/intent.json written with: steps[], variables[], task_type, complexity.
Phase 2: Resolve
Read phases/02-resolve.md and execute.
Objective: Map each intent step to a concrete executor node.
What ships with it
7 files 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.
- 1mo ago First seen · 154 lines · 55 tokens per session scan A ee8e863c720b
wf-composer is a skill published in the GitHub repository catlog22/Claude-Code-Workflow (2,124 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 1,188 once invoked, about $0.0002 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 skills, from other repositories
spk-run-implement-review
Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.
spk-team-sync
Operate Spec Kitty tracker sync (sync pull/sync push/sync run for local providers) and hosted SaaS-backed mission data.
spk-admin-dashboard
Open or report the Spec Kitty dashboard. Use for dashboard URL, localhost daemon metadata in .kittify/.dashboard, --open, --kill, or status views.
spk-gate-retrospective
Create or verify Spec Kitty mission retrospectives after merge and surface process learnings without blocking completed work.
spk-team-connectors
Operate Spec Kitty connector integrations and route connector work across tracker, sync, SaaS, and external services.
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.