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/deerwork-ai/deer-workflow/workflow-creatornpx skills add deerwork-ai/deer-workflow --skill workflow-creatorgit clone --depth 1 https://github.com/deerwork-ai/deer-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/deerwork-ai/deer-workflow/workflow-creator)<a href="https://agentmods.dev/skills/deerwork-ai/deer-workflow/workflow-creator"><img src="https://agentmods.dev/badge/skills/deerwork-ai/deer-workflow/workflow-creator.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.00066 | $0.02978 |
| Opus 5 | $0.00033 | $0.01489 |
| Sonnet 5 | $0.00013 | $0.00596 |
| Haiku 4.5 | $0.00007 | $0.00298 |
Grade A, and why
workflow-creator 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deer Workflow Creator
Translate the user's task into one complete, runnable Deer Workflow ESM module. The module coordinates work; it does not pretend that Deer Workflow injects functions into its global scope.
Establish the target
Infer these decisions from the request and existing repository context:
- A kebab-case Workflow name and one-line description.
- The input object accepted by the Workflow.
- The final value returned to the caller.
- The durable artifact file or files the Workflow should create.
- The phases visible in lifecycle events.
- Which operations are deterministic coordination and which require an Agent Loop's judgment or tools.
- Whether work is independent fan-out, an item-by-item pipeline, or a global stage followed by another fan-out.
Ask a question only when a missing answer would materially change whether the Workflow reads or modifies user data. Otherwise make the smallest reasonable assumption and state it in a short code comment.
Read the actual contract
Read references/api.md before generating code. It is the source of truth for the currently implemented API.
Read references/patterns.md when the request involves concurrency, multiple Agent calls, structured output, verification, file changes, or nested Workflows.
The essential runtime model is:
- Import APIs explicitly from
@deerwork-ai/deer-workflow. - Export a pure-literal
metaobject containingname,description,phases, andexampleArgs. - Export an
asynchandler asdefaultor as namedrun. - Receive caller input as the handler's first argument, named
args. - Optionally receive the Workflow execution context as the second argument.
- Let
WorkflowRunnerprovide lifecycle, phase, event, and logging context through async-local state.
Do not generate the older destructured-injection signature:
export default async function ({ agent, parallel, args }) {}
args is not a JavaScript global. It is the first Handler parameter. Naming it
args preserves the Dynamic Workflow vocabulary without pretending the
current runtime mutates globalThis.
What ships with it
4 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.
- 4d ago First seen · 319 lines · 66 tokens per session scan A 5b00e9783bf9
workflow-creator is a skill published in the GitHub repository deerwork-ai/deer-workflow (527 stars, last pushed 25d ago), licensed MIT. It adds 66 tokens to every session and 2,978 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-30.
Other skills, from other repositories
agent-spec-tool-first
CRITICAL: Use for agent-spec CLI tool workflow. Triggers on: agent-spec, contract, lifecycle, guard, verify, explain, stamp, checkpoint, plan, requirements, work-units, knowledge requirements, KLL, docs vs knowledge, spec verification, task contract, spec quality, lint spec, run log, "how to verify", "how to use…
importing-a-codebase
Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
agent-spec-authoring
CRITICAL: Use for writing and editing agent-spec .spec/.spec.md files. Triggers on: write spec, create spec, edit spec, new spec, spec authoring, task contract, .spec file, .spec.md file, BDD scenario, acceptance criteria, completion criteria, test selector, boundary, constraint, intent, decision, out of scope, "how…
agent-spec-estimate
CRITICAL: Use for estimating work effort from agent-spec Task Contracts. Triggers on: estimate, estimation, how long, work effort, round count, time estimate, scope, sizing, cost, budget, planning, sprint, capacity, "how many rounds", "how long will this take", "estimate this spec", 估算, 工作量, 多久, 时间估算, 预估, 工时, 规模…
agent-spec-intent-compiler
Use when converting PRD or issue prose into KLL requirements, running the intent compiler plan, or reverse-interviewing a human to resolve requirement ambiguity before task spec generation.