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 skills add subhansh-dev/agent-maxxing --skill 22-taskflowgit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWrote 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/subhansh-dev/agent-maxxing/22-taskflow)<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/22-taskflow"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/22-taskflow/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.
<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/22-taskflow"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/22-taskflow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00026 | $0.01117 |
| Opus 5 | $0.00013 | $0.00558 |
| Sonnet 5 | $0.00005 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00112 |
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 5d 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.
This is a copy
91% identical to taskflow — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 148 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.
- 5d ago First seen · 148 lines · 26 tokens per session scan A 34b4abb27e81
taskflow is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,117 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to taskflow, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
writing
A writing guide for turning verified facts and calculations into finished text for a specific audience. It follows the requested language, structure, and length.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…