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 pioneerdotai/pioneer --skill tasksgit clone --depth 1 https://github.com/pioneerdotai/pioneerWrote 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/pioneerdotai/pioneer/tasks)<a href="https://agentmods.dev/skills/pioneerdotai/pioneer/tasks"><img src="https://agentmods.dev/badge/skills/pioneerdotai/pioneer/tasks/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/pioneerdotai/pioneer/tasks"><img src="https://agentmods.dev/badge/skills/pioneerdotai/pioneer/tasks.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.00054 | $0.02644 |
| Opus 5.5 | $0.00022 | $0.01058 |
| Sonnet 5.5 | $0.00011 | $0.00529 |
| Haiku 4.5 | $0.00005 | $0.00264 |
Grade B, and why
tasks scanned grade B with 1 finding 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
For delivery fixes, preserve schedule, goal, instructions, and output instructions unless the user asked to change them. How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pioneer Durable Tasks
Durable tasks are product objects that can outlive the current turn. They have task state, run history, result snapshots, attempts, diagnostics, schedules, and delivery behavior.
When observing a task with task_get, distinguish task, run, and execution status. A running run is unfinished; no result or unchanged updatedAt does not prove a stall. The execution heartbeat is periodic liveness, while lastActivityAt is confirmed activity only when recorded. Missing activity is unknown. Do not cancel or repeat work solely because it is taking time or repeated observations are unchanged. A task_wait timeout ends only that wait window and permits another wait for active attached work.
Use this skill for future, recurring, background, or already-existing task work. For attached child agents created to help with the current turn, read system:pioneer/subagents instead.
Product Model
Think in three surfaces:
- Task state: durable source of truth for what should run, what did run, results, attempts, errors, and diagnostics.
- Run execution: a concrete attempt to perform the task now or later.
- Delivery: the policy that decides whether a terminal task result becomes a thread message, user notification, webhook call, or no visible output.
Do not confuse "the task produced a result" with "the user saw the result in this thread." Execution and delivery are separate.
Quick Start
Before using durable task tools, decide what kind of task work this is.
- If work should run later or repeatedly, use
task_createto create a scheduled, interval, or cron task with self-contained future-run instructions. - If existing task behavior must change, inspect it first with
task_getortask_list. - If only the schedule changes, use
task_reschedulewhen available. - If delivery changes, patch only delivery and verify it.
- If the task should be temporarily stopped or restarted, use pause/resume tools when visible.
- If the user asks to stop permanently while letting current work finish, use
task_finishwhen visible. Usetask_cancelwhen the user wants cancellation under its existing interruption rules. - If a result should appear in this chat later, configure thread delivery deliberately.
- If the result should only alert the user, use notification delivery only when a durable chat message is not required.
What ships with it
3 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 Changed · +2 lines ee66b100c6a7
- 5d ago Changed · +18 lines · +4 tokens per session 4d14cadc2559
- 8d ago Changed · +6 lines 1e47f312d55a
- 28d ago Changed · +4 lines 6d6b2af43b38
- 1mo ago Changed · +5 lines 4fd47f86827e
- 1mo ago First seen · 140 lines · 50 tokens per session scan B 8e0f5688a2b8
tasks is a skill published in the GitHub repository pioneerdotai/pioneer (22 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 2,644 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
tmux
Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).
reggeli-napindito
Reggeli összefoglaló: email, naptár, AI hírek, plus Dream Engine top-of-message.
linkding
Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.
folyamatos-ellenorzes
Ellenorizd: 1) Naptar - van-e meeting 1 oran belul? 2) Email - jott-e surgos level az elmult oraban? 3) Kanban - van-e mai hataridovel kartya? Ha BARMIT talalsz ami fontos, szolj a beallitott csatornan tomoren. Ha minden csendes, ne irj semmit.
radicale
This skill should be used when managing calendars and contacts on a self-hosted Radicale CalDAV/CardDAV server. Use when the user asks to "list my calendar", "what's on my calendar this week", "show me my events", "when is my next event", "add to my calendar", "create an event", "schedule a meeting", "schedule an…
memos
Manage notes and memos in self-hosted Memos service. Use when the user asks to "save this to memos", "create a memo", "search my memos", "find notes about X", "what did I write about", "add a note", "capture this", "remember this", "save this thought", or mentions note-taking, knowledge management, or personal notes.