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/blocunited-llc/mozaiks/create-workflownpx skills add BlocUnited-LLC/mozaiks --skill create-workflowgit clone --depth 1 https://github.com/BlocUnited-LLC/mozaiksWrote 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/blocunited-llc/mozaiks/create-workflow)<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="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.00024 | $0.01740 |
| Opus 5 | $0.00012 | $0.00870 |
| Sonnet 5 | $0.00005 | $0.00348 |
| Haiku 4.5 | $0.00002 | $0.00174 |
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 4d 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 — 261 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 or branch off it instead of 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[]inextended_orchestration/extension_registry.json= cross-workflow build/revision sequencing.transitions[]inextended_orchestration/extension_registry.json= user choice and context-seeding routes.entrypoints[]inextended_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.
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.
- 4d ago First seen · 261 lines · 24 tokens per session scan A 527241a7f6f6
create-workflow is a skill published in the GitHub repository BlocUnited-LLC/mozaiks (25 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 1,740 once invoked, about $0.0001 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-30.
Other skills, from other repositories
add-new-model
Add support for a newly-released LLM model in pydantic-ai (e.g. openai:gpt-5.6, anthropic:claude-sonnet-5). Use when a provider ships a new model id and you need to wire literals, profile flags, and tests to recognize it. Handles SDK-lag, gateway list conventions, and capability probing.
building-pydantic-ai-agents
Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydanticai, or asks to build an AI agent, add tools/capabilities, defer capability loading, stream output, define agents…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
testing-skill
Record, rewrite, and debug VCR cassettes for HTTP recordings. Use when running tests with --record-mode, verifying cassette playback, or inspecting request/response bodies in YAML cassettes.
pre-push-review
Run a high-judgment local review of the current branch before pushing, both before a PR exists and between PR iterations.
adding-a-provider-api-feature
Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI. Use when wiring a provider feature through the library — it enforces reasoning from the existing cross-provider abstraction before designing…