What is create-workflow?

A guide for creating a new AI workflow from the user's requirements. It produces workflow configuration, tools, and optional interface components under the correct application or shared factory location.

Use it to plan and build standalone workflows or workflows that connect to other workflows, choosing the correct project location and authoring structure.

It turns an informal idea into a defined workflow with clear agents, typed outputs, stored data, and generated interface artifacts.

How BlocUnited-LLC/mozaiks configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to BlocUnited-LLC/mozaiks. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/BlocUnited-LLC/mozaiks/main/.agents/skills/create-workflow/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/BlocUnited-LLC/mozaiks

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/create-workflow/github.svg)](https://agentmods.dev/skills/blocunited-llc/mozaiks/create-workflow)

Your own site

<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/create-workflow"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/create-workflow/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/blocunited-llc/mozaiks/create-workflow"><img src="https://agentmods.dev/badge/skills/blocunited-llc/mozaiks/create-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,840 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.01840
Opus 5.5	$0.00010	$0.00736
Sonnet 5.5	$0.00005	$0.00368
Haiku 4.5	$0.00002	$0.00184

Measured 26d ago against content hash 4a0204ebddd8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 26d 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.

.agents/skills/create-workflow/SKILL.md · 268 lines

How it starts

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

Before starting: git fetch origin && gh pr list --state open && git log origin/main --oneline -3 — if another agent has an open PR touching the same files you need, wait for it to merge, then branch from fresh origin/main.

Help the user create a new workflow named $ARGUMENTS.

When acting on this skill, transform human intent into a deterministic workflow bundle that matches the current Mozaiks workflow authoring contract.

First Decision: Which Workflow Root Owns It?

Choose the owning workflow root before writing files:

App-owned workflows belong under app/workflows/{WorkflowName}/.
Shared factory/builder workflows in this repo belong under factory_app/workflows/{WorkflowName}/.

Do not treat every workflow as an app-owned workflow by default.

Phase 1: Architectural Discovery

Before writing any files, define the deterministic contract:

What outcome must the workflow produce?
Which agents are needed, and which ones are conversational vs structured-output agents?
What exact typed outputs must the workflow emit?
Which tools persist data or emit UI artifacts?
Is the workflow standalone, part of a cross-workflow sequence, or using workflow-local task batches?
Which context variables are required at startup or on resume?

Routing Model: Do Not Mix These Up

Mozaiks has multiple routing layers. Keep them separate:

transition_graph.yaml = workflow-local agent routing inside one workflow.
workflow_sequences[] in extended_orchestration/extension_registry.json = cross-workflow build/revision sequencing.
transitions[] in extended_orchestration/extension_registry.json = user choice and context-seeding routes.
entrypoints[] in extended_orchestration/extension_registry.json = external route entry into a sequence or transition.

Important:

A workflow sequence is not a human-in-the-loop handoff mechanism.
A transition is not an agent handoff.
Do not try to encode build-sequence policy inside transition_graph.yaml.

Read the full file on GitHub · 268 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.

26d ago Changed 4a0204ebddd8
1mo ago Changed · +5 lines ebc50e60cd7a
2mo ago Changed · +2 lines e5f2f7685bc4
2mo ago First seen · 261 lines · 24 tokens per session scan A 527241a7f6f6

Subscribe to this mod's changes

create-workflow is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (24 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,840 once invoked, about $0.0001 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-08-30.

Building agents LLM agent-framework agentic-ai ai ai-agents genai

create-workflow next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
create-workflowBlocUnited-LLC/mozaiks	Skill	24	yesterday	MIT	A	24	Claude Code
building-pydantic-ai-agentspydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	92	Claude Code, Codex
pydantic-ai-harnesspydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	197	Claude Code, Codex
migrating-langchain-to-pydantic-aipydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	100	Codex
migrating-vercel-ai-sdk-and-eve-to-pydantic-aipydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	107	Codex
migrating-claude-agent-sdk-to-pydantic-aipydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	90	Codex
migrating-mastra-to-pydantic-aipydantic/pydantic-ai	Skill	21k	yesterday	MIT	A	73	Codex

mozaiks: Skill for Claude Code