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 agentproto/ts --skill supervise-long-missionsgit clone --depth 1 https://github.com/agentproto/tsWrote 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/agentproto/ts/supervise-long-missions)<a href="https://agentmods.dev/skills/agentproto/ts/supervise-long-missions"><img src="https://agentmods.dev/badge/skills/agentproto/ts/supervise-long-missions/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/agentproto/ts/supervise-long-missions"><img src="https://agentmods.dev/badge/skills/agentproto/ts/supervise-long-missions.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.00074 | $0.00340 |
| Opus 5 | $0.00037 | $0.00170 |
| Sonnet 5 | $0.00015 | $0.00068 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
supervise-long-missions 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.
What it actually says
supervise-long-missions
For missions that outlive your attention. Each row names the primitive that owns the mechanics; open it for tool signatures and recipes.
| I want… | Open |
|---|---|
| Non-blocking notification when work completes | ap-wait-durable |
| Completion gates with automatic retry nudges | ap-policies |
| Scheduled check-ins re-pinging my own session | ap-cron (kind prompt-session) |
| A shared board with claim semantics for workers | ap-tasks |
| Spend tracking and windowed cost estimates | ap-models-auth |
| Cleanup when the mission ends | ap-lifecycle |
Playbooks that assemble these steps end-to-end:
- Parallel workers with fan-in and durable waiting →
pb-supervise-parallel-mission. - Boss-style scheduled check-ins into one session →
pb-boss-checkins.
Start here if a mission will run longer than this conversation: arm
ap-wait-durable first, add ap-policies for quality gates, then ap-cron
(kind prompt-session) for periodic check-ins.
Golden rule: arm the watch AT spawn time; wakeup timers are a safety net, never the mechanism.
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 · 31 lines · 74 tokens per session scan A 01b5c0180d77
supervise-long-missions is a skill published in the GitHub repository agentproto/ts (5 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 340 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-09-04.
Other skills, from other repositories
github-triage
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
backlog
Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug…
reframe-voice
Write, rewrite, or review content in the evidence-led reframe voice style. Use when the user explicitly asks to write in "reframe voice" or "reframe style". Do NOT use for general writing tasks.
to-tickets
Break a plan, spec, or the current conversation into independently-grabbable tickets on the project issue tracker using tracer-bullet vertical slices, each declaring the tickets that block it. Use when user wants to convert a plan or spec into tickets, create implementation tickets, or break down work into issues.
to-spec
Turn the current conversation context into a spec and submit it as a GitHub issue. Use when user wants to create a spec or PRD from the current context.
qa-to-issues
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Use when user wants to report bugs in their own codebase and create Github issues conversationally.