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/the-open-agent/openagent/taskflownpx skills add the-open-agent/openagent --skill taskflowgit clone --depth 1 https://github.com/the-open-agent/openagentWhat 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.00080 | $0.01202 |
| Opus 5 | $0.00040 | $0.00601 |
| Sonnet 5 | $0.00016 | $0.00240 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
taskflow 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- taskflow — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TaskFlow
Use TaskFlow when a job needs to outlive one prompt or one detached run, but you still want one owner session, one return context, and one place to inspect or resume the work.
When to use it
- Multi-step background work with one owner
- Work that waits on detached ACP or subagent tasks
- Jobs that may need to emit one clear update back to the owner
- Jobs that need small persisted state between steps
- Plugin or tool work that must survive restarts and revision conflicts cleanly
What TaskFlow owns
- flow identity
- owner session and requester origin
currentStep,stateJson, andwaitJson- linked child tasks and their parent flow id
- finish, fail, cancel, waiting, and blocked state
- revision tracking for conflict-safe mutations
It does not own branching or business logic. Put that in Lobster, acpx, or the calling code.
Current runtime shape
Canonical plugin/runtime entrypoint:
api.runtime.tasks.flowapi.runtime.taskFlowstill exists as an alias, butapi.runtime.tasks.flowis the canonical shape
Binding:
api.runtime.tasks.flow.fromToolContext(ctx)when you already have trusted tool context withsessionKeyapi.runtime.tasks.flow.bindSession({ sessionKey, requesterOrigin })when your binding layer already resolved the session and delivery context
Managed-flow lifecycle:
createManaged(...)runTask(...)setWaiting(...)when waiting on a person or an external systemresume(...)when work can continuefinish(...)orfail(...)requestCancel(...)orcancel(...)when the whole job should stop
Design constraints
- Use managed TaskFlows when your code owns the orchestration.
- One-task mirrored flows are created by core runtime for detached ACP/subagent work; this skill is mainly about managed flows.
- Treat
stateJsonas the persisted state bag. There is no separatesetFlowOutputorappendFlowOutputAPI. - Every mutating method after creation is revision-checked. Carry forward the latest
flow.revisionafter each successful mutation. runTask(...)links the child task to the flow. Use it instead of manually creating detached tasks when you want parent orchestration.
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.
- 2d ago First seen · 150 lines · 80 tokens per session scan A 74d4e9c76f24
taskflow is a skill published in the GitHub repository the-open-agent/openagent (5,596 stars, last pushed today), licensed Apache-2.0. It adds 80 tokens to every session and 1,202 once invoked, about $0.0004 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
greeting-user
Explains how to properly greet the user.
using-process-tool
Describes how to correctly use 'process' tool.
cherry-pick-pro
Cherry-pick commits from chatbox-pro repo to the open chatbox repo, handling mobile-only files, package name differences, and other repo-specific exclusions.
test-skill
test description.
i18n-translate
翻译 Chatbox Pro 当前未提交改动、暂存改动或用户指定 commit/range 中新增或受影响的 i18n key。当用户要求翻译、补全与改动 UI 文案相关的翻译时使用。Agent 需要阅读 diff 和组件上下文，遵守 skill 内置 glossary，并直接写 locale JSON；脚本只用于最后校验。.
documents
Create, read, edit, review, comment on, sanitize, render, and validate Microsoft Word DOCX documents. Use whenever a DOCX or Word document is a primary input or deliverable, including reports, proposals, forms, templates, tracked revisions, comments, tables, images, headers, footers, and style-preserving edits.