create-workflow

A guided designer for YAML workflows, which are written step-by-step processes with named stages and rules for moving between them. It can define which tools and permission levels are available at each stage.

In plain words
What is it for?
Building controlled flows such as plan, implement, review, and verify for code changes, or gather, analyze, validate, and present for research.
Why use it?
It helps enforce processes that must happen in order instead of relying only on an agent to remember the instructions.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/gettalon/talon-plugins/create-workflow
Any agent
npx skills add gettalon/talon-plugins --skill create-workflow
Clone the repo
git clone --depth 1 https://github.com/gettalon/talon-plugins

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,270 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00052 $0.01270
Opus 5 $0.00026 $0.00635
Sonnet 5 $0.00010 $0.00254
Haiku 4.5 $0.00005 $0.00127

Measured 2d ago against content hash 6ddec6ee0da1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-workflow 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 2d 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.

plugins/agent-factory/skills/create-workflow/SKILL.md · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Workflow — State Machine Designer

Design a YAML workflow that enforces a multi-step process with state transitions, per-state tool restrictions, and permission modes.

When to Use Workflows vs Skills

Use a Skill Use a Workflow
Repeatable task with steps Process with enforced stages
Agent follows instructions voluntarily System enforces what tools are available per stage
No state tracking needed State tracked across interactions
e.g., "Run a DCF valuation" e.g., "Plan → Implement → Review → Ship"

Rule of thumb: If the agent must NOT skip a stage or use certain tools before completing a prior stage, use a workflow. If it's guidance the agent follows, use a skill.

Process

Step 1: Understand the Process

Ask one at a time:

  1. What process does this workflow enforce?

    • e.g., "Code change: plan → implement → review → verify"
    • e.g., "Research: gather → analyze → validate → present"
    • e.g., "Incident: triage → investigate → remediate → postmortem"
  2. What are the stages (states)?

    • List each stage and what happens there
    • What marks a stage as complete (transition condition)?
  3. Should tools be restricted per stage?

    • e.g., Planning stage: read-only tools only
    • e.g., Review stage: no file writes
    • e.g., Implementation: all tools available
  4. What permission mode per stage?

    • plan — read-only, agent proposes but doesn't act
    • ask — agent asks before each action
    • allow — agent can read/write freely
    • bypass — full autonomy including shell execution

Step 2: Design the State Machine

Map out states and transitions:

[initial] → [state-2] → [state-3] → [done]
              ↑                        |
              └────── (rejected) ──────┘

For each state, define:

  • name: Short identifier (snake_case)
  • allowed_tools: Tool allowlist (null = all)
  • permission_mode: plan | ask | allow | bypass (optional, derived from tools if omitted)
  • on_entry: Instructions when entering this state
  • on_exit: Cleanup when leaving (optional)
  • transitions: List of possible next states with optional conditions

Read the full file on GitHub · 177 lines

Changes

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.

  1. 2d ago First seen · 177 lines · 52 tokens per session scan A 6ddec6ee0da1

Subscribe to this mod's changes

create-workflow is a skill published in the GitHub repository gettalon/talon-plugins (6 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 1,270 once invoked, about $0.0003 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.