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/sawy3r/baton/baton-implementnpx skills add sawy3r/baton --skill baton-implementgit 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-implement)<a href="https://agentmods.dev/skills/sawy3r/baton/baton-implement"><img src="https://agentmods.dev/badge/skills/sawy3r/baton/baton-implement.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.1 | $0.00013 | $0.00666 |
| Opus 5 | $0.00006 | $0.00333 |
| Sonnet 5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
baton-implement 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.
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-implement version: baton.operation/v2
Purpose
Explain an approach or build one slice without taking the Captain or Verifier role.
Inputs
- Approved plan, revision, slice, and attempt.
- Dependencies, inputs, scope, acceptance, checks, limits, and exclusions.
- Captain decision and any prior Verifier decision.
Authority
Stay within the approved slice and attempt. Building requires PROCEED for its
plan, slice, and design. REVISE adds a design attempt; FAIL adds an
implementation attempt. Neither replaces the slice.
Scope commits behavior and product, not every path. Support paths and checks are evidence unless they change behavior, consumed product, contract, authority, or an outside decision.
Product code, build, test, package, deploy, hooks, and runtime MUST NOT read or
depend on reserved .baton/releases; do not modify it.
Actions
- Before design, use the current plan and exact base prepared from passed consumed work. Older track records are history. Return a design TL;DR mapping every acceptance ID to the approach and proposed evidence. Name risks or missing requirements. Stop; invent nothing.
- After
PROCEED, check the base again. Build the approved result, apply bounded corrections, preserve the record root, and repair priorFAILon the same slice. - Run required and useful checks. Inspect the diff, candidate, product identity, and evidence.
- Return acceptance-linked evidence over the exact candidate, support paths, and extra results. Stop.
Required output
Lead with result, meaning, and next step. After design, include the Captain
handoff. After implementation, include checks, acceptance evidence, deviations,
and the Verifier handoff. Put revision, slice, attempt, exact binding, candidate,
and product identities under technical details. Never write receipts or claim
PASS.
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 · 80 lines · 13 tokens per session scan A ff9112576af7
baton-implement is a skill published in the GitHub repository sawy3r/baton (9 stars, last pushed 27d ago), licensed MIT. It adds 13 tokens to every session and 666 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
统一创建、改写、品牌化或忠实转载微信公众号文章包：正文写作调用唯一文风与作者性能力，离线完成结构、品牌、封面、4:3 首图、来源与质量验收。Use when asked to write, brand, audit, or faithfully repost a WeChat 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…