building-a-workflow-spell

building-a-workflow-spell is a skill for Claude Code from redhuntlabs/wizard. It costs 33 tokens per session (1,178 once invoked), scanned A, original, MIT.

A builder for multi-stage agent workflows, where each stage produces something for the next stage to use.

In plain words
What is it for?
Use it to create a workflow spell with named stages, handoff materials, checkpoints, and loop-back rules.
Why use it?
It helps turn a loosely described process into clear stages with review points and conditions for going back to an earlier stage.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the wizard plugin — 37 skills, 6 commands, 1 agent, 1 hook shipped together

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/redhuntlabs/wizard/building-a-workflow-spell
Any agent
npx skills add redhuntlabs/wizard --skill building-a-workflow-spell
Clone the repo
git clone --depth 1 https://github.com/redhuntlabs/wizard

Made for: Claude Code.

Or install wizard, the plugin that ships this one along with the rest of its 37 skills, 6 commands, 1 agent, 1 hook.

Wrote 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.

agentmods badge for building-a-workflow-spell

README.md
[![agentmods](https://agentmods.dev/badge/skills/redhuntlabs/wizard/building-a-workflow-spell.svg)](https://agentmods.dev/skills/redhuntlabs/wizard/building-a-workflow-spell)
Your own site
<a href="https://agentmods.dev/skills/redhuntlabs/wizard/building-a-workflow-spell"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/building-a-workflow-spell.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,178 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.1 $0.00033 $0.01178
Opus 5 $0.00016 $0.00589
Sonnet 5 $0.00007 $0.00236
Haiku 4.5 $0.00003 $0.00118

Measured 6d ago against content hash ddd50f58f1d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

building-a-workflow-spell 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 6d 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.

skills/building-a-workflow-spell/SKILL.md · 146 lines

How it starts

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

Building a Workflow Spell

What this does

Specialist builder for kind: workflow spells. A workflow has multiple stages with explicit handoff artifacts and checkpoints between them.

When to use

  • Routed to from building-a-spell Stage 2 when kind: workflow
  • User describes a process with natural stopping points and intermediate artifacts

What you bring (Inputs)

  • The workflow's overall goal
  • The natural stages (or the steps the user does today, which we'll cluster)
  • The artifact handed from each stage to the next

What you get (Output)

A draft SKILL.md with explicit Stages, Checkpoints, and Loop-back conditions sections, ready for the standard tester.

How it works (Steps)

This is a workflow chain.

Stages

Stage 1: Identify the natural stopping points

A stage is a place where you could (and sometimes do) stop, hand the work to someone else, and return to it later.

Ask the user (or extract): "What are the natural stopping points in this process?"

If the user says "no stopping points, it's one continuous flow" — this isn't a workflow; it's a content kind. Re-route.

Stage 2: Name each stage and its artifact

Each stage has:

  • Goal: what this stage accomplishes
  • Input: artifact from the previous stage (or initial inputs for stage 1)
  • Output: artifact handed to the next stage

If you can't name the output artifact, the stage isn't well-defined yet. Sharpen.

Stage 3: Write checkpoints

For each stage transition, write the checkpoint — what must be true to pass the gate.

Checkpoints are tested, not asserted. Each checkpoint should be verifiable: the artifact has a property you can check.

Stage 4: Identify loop-back conditions

A workflow without loop-backs is a pipeline (one-way). Most real workflows loop back — when the artifact at stage N reveals stage N-1 was wrong.

Capture loop-back conditions explicitly. If there are none, that's a finding — confirm with user.

Stage 5: If the workflow composes other spells, declare them

Read the full file on GitHub · 146 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. 6d ago First seen · 146 lines · 33 tokens per session scan A ddd50f58f1d6

Subscribe to this mod's changes

building-a-workflow-spell is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 1,178 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-08-31.