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/stablebaseline/mcp/sb-plannpx skills add stablebaseline/mcp --skill sb-plangit clone --depth 1 https://github.com/stablebaseline/mcpWrote 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/stablebaseline/mcp/sb-plan)<a href="https://agentmods.dev/skills/stablebaseline/mcp/sb-plan"><img src="https://agentmods.dev/badge/skills/stablebaseline/mcp/sb-plan.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.00113 | $0.02032 |
| Opus 5 | $0.00056 | $0.01016 |
| Sonnet 5 | $0.00023 | $0.00406 |
| Haiku 4.5 | $0.00011 | $0.00203 |
Grade A, and why
sb-plan 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 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.
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stable Baseline: plans and tasks
What this skill does
Builds and maintains structured plans: phases, tasks, dependencies, assignees and dates. Every change runs under the signed in user's own Stable Baseline identity.
IDs are never hardcoded. Resolve projectId, planId, phaseId and task IDs at
runtime from listing calls made in this conversation.
The hierarchy
Project contains plans, a plan contains phases, a phase contains tasks. Work down it, never guess a level.
listPlansrequiresprojectIdlistPlanPhasesandgetPlanHierarchyfor the structurelistTasksrequiresplanId
Before you change anything
- Resolve scope.
listOrganisations,listWorkspaces,listProjects. Ask if several projects are accessible. - Check what exists.
listPlanswith aquerybefore creating a plan.listTasksbefore adding a task that may already be there. Duplicate tasks are the most common failure when working from a transcript. - Read the current state before editing.
getPlan,getPlanPhaseorgetTaskso you know what you are changing.
Creating
createPlanrequiresprojectIdandtitle. It also takesdescription,status,priority,start_date,end_dateandlinked_documents. Link the source document when there is one; it is what makes the plan traceable.createPlanPhasefor a phase.createTaskrequiresplanIdandtitle. It also takesphaseId,description,type,status,priority,acceptance_criteriaandchecklist.
acceptance_criteria and checklist both replace the whole array on update, and array
order is display order. To change one row, fetch the item with getTask, modify the array,
and send the whole thing back. Echo back each existing row id you keep, so the server's
per-row attribution, who added or completed it and when, survives the round trip.
Write real acceptance criteria when the user has given you enough to work with. A task titled "fix auth" with no criteria helps nobody.
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 First seen · 186 lines · 113 tokens per session scan A b07795f75c54
sb-plan is a skill published in the GitHub repository stablebaseline/mcp (0 stars, last pushed 8d ago), licensed MIT. It adds 113 tokens to every session and 2,032 once invoked, about $0.0006 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-31.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
okx-task-watch
监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 / 继续监听 / task watch / user watch / monitor task progress / catch me up on tasks / outstanding decisions — OKX A2A user-session task-notification monitor: live long-poll via okx-a2a user watch (also drains backlog of past/missed/unread events on entry) plus…
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.