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/jeomon/operator-use/workflow-buildernpx skills add Jeomon/Operator-Use --skill workflow-buildergit clone --depth 1 https://github.com/Jeomon/Operator-UseWhat 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.00062 | $0.02699 |
| Opus 5 | $0.00031 | $0.01350 |
| Sonnet 5 | $0.00012 | $0.00540 |
| Haiku 4.5 | $0.00006 | $0.00270 |
Grade A, and why
workflow-builder 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 3d 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Builder
When the user asks you to create, build, or generate a workflow, use this skill to produce a correct .py workflow file and save it to the workflows directory.
Workflow file format
Every workflow file has:
- A top-level
metadict withname,description,when_to_use, and optionalphaseslist. - An
async def run()entry point. - DSL globals injected at runtime — never import them.
Available DSL globals:
| Global | Purpose |
|---|---|
await agent(prompt, schema=None, system=None, tools=None, resume=False, stall_ms=180000, max_retries=5, model=None, provider=None) |
Full subagent turn with tool execution. Returns str or Pydantic instance. |
await classify(prompt, *, options=None, schema=None, system=None, model=None, provider=None) |
Single direct LLM call — no tool loop. Use for routing/labelling. Returns str (options) or Pydantic instance (schema). |
await parallel(*thunks, concurrency=5, return_exceptions=False) |
Run zero-arg async callables concurrently. |
await pipeline(items, *stages, concurrency=5) |
Pass each item through staged transforms. |
await workflow(name, args=None) |
Run another workflow inline (one level deep). |
async with phase("name"): |
Label the current phase in run status. |
log("message") |
Append timestamped line to run log. |
budget |
.spent() / .remaining() / .exhausted() / .tokens_spent() — call count + token tracking. |
args |
dict of invocation arguments. |
Pattern catalogue
Pick the right pattern based on the user's description. Generate the full .py file for the chosen pattern.
1. Classify-and-act
Route input to specialized handlers based on a cheap single-call classification.
meta = {
"name": "classify-and-act",
"description": "Route a task to a specialized handler based on its type.",
"when_to_use": "Input could be one of several distinct task types each needing different handling.",
"phases": [
{"name": "classify", "description": "Determine task type"},
{"name": "execute", "description": "Run the appropriate handler"},
],
}
async def run():
task = args.get("task", "")
async with phase("classify"):
kind = await classify(
f"Classify this task into one category.\nTask: {task}",
options=["research", "code", "summarize", "other"],
model="claude-haiku-4-5",
)
log(f"classified as: {kind}")
async with phase("execute"):
if kind == "research":
return await agent(f"Research the following thoroughly:\n{task}")
elif kind == "code":
return await agent(f"Write code to accomplish:\n{task}")
elif kind == "summarize":
return await agent(f"Summarize the following:\n{task}")
else:
return await agent(task)
What ships with it
5 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.
- 3d ago First seen · 326 lines · 62 tokens per session scan A 6d2ba960b946
workflow-builder is a skill published in the GitHub repository Jeomon/Operator-Use (40 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 2,699 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
cli-docs-guidelines
Review or write CLI documentation. Enforces progressive disclosure, logical command ordering, and plain-language explanations. Use when asked to "write CLI docs", "document commands", "review CLI reference", or "update command docs".
readme-guidelines
Review or write README content for open-source projects. Enforces progressive disclosure, jargon-free language, and single-concept code examples. Use when asked to "write README", "review README", "update README", or "check docs".
unbrowse
The action engine of the internet. Unbrowse is the open-source action layer for AI agents: it learns a site's internal API routes from real browsing, then replays them as fast, cheap, indexed routes (cache hit under 200ms) instead of re-driving a browser. Capture once, replay everywhere. The default agent flow is ONE…
unbrowse
The action engine of the internet. Unbrowse is the open-source action layer for AI agents: it learns a site's internal API routes from real browsing, then replays them as fast, cheap, indexed routes (cache hit under 200ms) instead of re-driving a browser. Capture once, replay everywhere. The default agent flow is ONE…
ai-deploy
Deploy a generated project (one process or several) to agent-sandboxes with scale-to-zero: idle sandboxes pause and auto-resume (process restarted) on the next HTTP request. Use when asked to deploy, host, or preview generated code through the sandbox platform.
e2b-sandbox
Create, manage, and use E2B sandboxes — run commands, manage files, use git, persist state, and configure networking. Use when building agent workflows that need isolated execution environments.