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 sawy3r/baton --skill baton-plangit clone --depth 1 https://github.com/sawy3r/batonWrote 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/sawy3r/baton/baton-plan)<a href="https://agentmods.dev/skills/sawy3r/baton/baton-plan"><img src="https://agentmods.dev/badge/skills/sawy3r/baton/baton-plan/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/sawy3r/baton/baton-plan"><img src="https://agentmods.dev/badge/skills/sawy3r/baton/baton-plan.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.00016 | $0.00699 |
| Opus 5 | $0.00008 | $0.00349 |
| Sonnet 5 | $0.00003 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
baton-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 9d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use the invoking request as input. Resolve relative files from this directory. This standalone skill needs no shared Baton folder.
operation: baton-plan version: baton.operation/v2
Purpose
Turn a goal into a clear contract for someone else to approve. Planning never approves itself.
Inputs
- Goal, repository, target, approver, and applicable plan.
- Current repository, scope, acceptance, dependencies, inputs, limits, and exclusions.
Authority
Keep the release while its goal, target, and approver stay the same. Preserve unchanged slices and identify consumers of changed inputs. Approval must cover the exact release skeleton and every declared slice file.
The plan is a commitment. Support paths, additional checks, evidence, scheduling, retries, worktrees, and bookkeeping need no revision when the promise stays the same.
Actions
- Inspect Git, the plan, code, tests, docs, and history. Find repository facts.
- Ask only about human choices that could change the result. Offer no plan while one is open.
- When clear, summarize result, scope, acceptance, inputs, and limits; ask for correction or confirmation, then stop without plan bytes.
- Later, write a plan or forward-only revision with
templates/plan.mdand onetemplates/slice.mdper slice. Keep paths, digests, outcomes, and identities. Give each slice falsifiable acceptance. Declare everyscope.includepath intouchpoints, assigned to the track; shared paths require dependency. Optionally publish a human-readable bundle under configuredrelease_docs_root(defaultdocs/baton/releases) at<release>/slices/<id>/. Set it in the project.baton/config.jsonor the global~/.config/baton/config.json; project configuration overrides global configuration. Usetemplates/evidence.jsonas an advisory inventory. - Present the exact plan bytes for external approval and stop.
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.
- 9d ago First seen · 80 lines · 16 tokens per session scan A b0bbbf978665
baton-plan is a skill published in the GitHub repository sawy3r/baton (9 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 699 once invoked, about $0.0001 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
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
lov-article-creator
A skill that turns source material or a draft into a complete, branded WeChat public-account article package.
lov-repo2docs
Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…