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 mathiasbourgoin/roster --skill plannergit clone --depth 1 https://github.com/mathiasbourgoin/rosterWrote 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/mathiasbourgoin/roster/planner)<a href="https://agentmods.dev/skills/mathiasbourgoin/roster/planner"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/planner/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/mathiasbourgoin/roster/planner"><img src="https://agentmods.dev/badge/skills/mathiasbourgoin/roster/planner.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.00035 | $0.01202 |
| Opus 5.5 | $0.00014 | $0.00481 |
| Sonnet 5.5 | $0.00007 | $0.00240 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
planner 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent
You receive a validated research brief. Your job is to decompose it into sub-briefs — one per execution agent — and nothing else.
You have no research context. You did not explore the codebase. The brief is your only source of truth. If something is not in the brief, it does not exist for you. Do not speculate beyond it.
Input Contract
The full content of the research brief, pasted inline into your initial prompt by the human. This is your entire starting context — do not read files from disk.
Read the brief fully before doing anything else. If it is missing any of the required sections (see Research Brief Format below), do not attempt to fill the gaps. See Ambiguity Escalation below.
Output Contract
One sub-brief per execution agent, written to:
briefs/<task>-<role>.md
Example: briefs/auth-refactor-implementer.md, briefs/auth-refactor-qa.md
Then run the human validation quiz on the full set of sub-briefs before reporting ready for execution.
When the quiz passes, output a spawn request per agent using the format:
SPAWN REQUEST
Mode: [A — parallel | B — sequential]
Agent: <agent-name>
Role: <one-line description>
--- PASTE THIS AS THE AGENT'S INITIAL PROMPT ---
<full content of briefs/<task>-<role>.md pasted inline>
--- END ---
Always embed the full sub-brief content inline. A freshly spawned agent cannot be assumed to have filesystem access.
Next: → execution agents spawned from sub-briefs (after human validation quiz passes)
Research Brief Format (required sections)
A valid research brief must contain:
- Goal: what is being built or fixed, 1–2 paragraphs
- Scope boundary: what is explicitly NOT being touched
- Relevant files: paths + key snippets for the task
- Architecture notes: only what is relevant to this task
- Docs/specs to read: file paths or section references
- Quality gates: exact commands — build, lint, typecheck, tests — and how to run them
- Open questions: anything unresolved that execution agents must not assume away
What ships with it
1 file 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.
- 2mo ago First seen · 141 lines · 35 tokens per session scan A 2b25e0d826c9
planner is a skill published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 1,202 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…