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/heyhuynhgiabuu/openpi/task-toolnpx skills add heyhuynhgiabuu/openpi --skill task-toolgit clone --depth 1 https://github.com/heyhuynhgiabuu/openpiWrote 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/heyhuynhgiabuu/openpi/task-tool)<a href="https://agentmods.dev/skills/heyhuynhgiabuu/openpi/task-tool"><img src="https://agentmods.dev/badge/skills/heyhuynhgiabuu/openpi/task-tool.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.00056 | $0.00531 |
| Opus 5 | $0.00028 | $0.00266 |
| Sonnet 5 | $0.00011 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
task-tool 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.
What it actually says
Rules (matches pi-task v0.2.0)
- Never pass
task_idon a fresh delegation. Omit the field.task_idis for resuming an existing background task only. - Never pass
conversation_idunless the user explicitly asked for a durable specialist conversation. - Never invent UUIDs as
task_idoragent_id. The tool will reject them. - Only use a
task_idthat came back in a successful priortaskresult. Never reuse one from an error message or old history. - If a
taskcall returnsUnknown task_id: "...", re-issue withouttask_idand withoutconversation_id.
Call shapes
Fresh:
{ "agent_type": "scout", "description": "Research X", "prompt": "..." }
Background (default in pi-task):
{ "agent_type": "scout", "description": "Research X", "background": true, "prompt": "..." }
Resume (only with a valid task_id from a prior result):
{ "agent_type": "scout", "task_id": "m1lxyz-a1b2", "description": "Continue", "prompt": "..." }
Durable conversation (only when the user asked for one):
{ "agent_type": "scout", "conversation_id": "research-ai", "description": "Continue", "prompt": "..." }
Anti-patterns
task_idon a fresh call.task_idas a UUID.conversation_idwithout the user asking.- Resuming a task that was never successfully started.
Error recovery
| Error | Fix |
|---|---|
Unknown task_id: "..." |
Re-issue without task_id (fresh task) or use a conversation_id |
Unknown agent: "..." |
Use one of: scout, explore, planner, reviewer, vision, worker |
task_id/conversation_id mismatch |
Use the task_id that maps to your conversation_id |
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 · 50 lines · 56 tokens per session scan A 692e8a2574a7
task-tool is a skill published in the GitHub repository heyhuynhgiabuu/openpi (212 stars, last pushed 22d ago), licensed MIT. It adds 56 tokens to every session and 531 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…