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 sandbaseai/sandbase-skills --skill finishing-a-development-branchgit clone --depth 1 https://github.com/sandbaseai/sandbase-skillsWrote 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/sandbaseai/sandbase-skills/finishing-a-development-branch)<a href="https://agentmods.dev/skills/sandbaseai/sandbase-skills/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/sandbaseai/sandbase-skills/finishing-a-development-branch/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/sandbaseai/sandbase-skills/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/sandbaseai/sandbase-skills/finishing-a-development-branch.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.00044 | $0.00608 |
| Opus 5.5 | $0.00018 | $0.00243 |
| Sonnet 5.5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
finishing-a-development-branch 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 28d 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.
This is a copy
72% identical to accessibility-review — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finishing A Development Branch
Use this Skill to produce a bounded, verifiable Finishing A Development Branch outcome. Preserve the user's chosen stack, source material, and authorization boundaries.
Read the SandBase API map only when the task genuinely needs an external data source or generative model.
Workflow
- Inspect the available files, runtime, versions, inputs, and existing conventions before deciding what to change.
- Restate the requested outcome, constraints, acceptance checks, and any assumption that could change the result.
- Produce the smallest complete implementation, analysis, or artifact that satisfies those checks.
- Verify the real output with appropriate tests, previews, calculations, or source comparison; do not infer success from file creation alone.
- Return the deliverable, evidence of validation, material assumptions, and unresolved limitations.
Quality gates
- Inspect repository instructions, current versions, tests, and user changes before proposing an implementation.
- Make the smallest compatible change, preserve public contracts unless change is requested, and avoid new dependencies without a concrete benefit.
- Run focused tests plus the relevant build or static checks, then report observed results and any unverified paths.
- Do not stage, commit, push, open a pull request, tag, publish, or discard changes unless the user requested that exact action.
SandBase boundary
Keep the core Finishing A Development Branch work local. Use SandBase only for current external documentation, repository evidence, or explicitly requested model inference.
- Call
sandbase_discoverwith a short capability query. - Call
sandbase_inspectfor viable candidates and compare the live schema, coverage, limits, output, execution mode, and price. - Prefer a dedicated tool or API the user already has. Send only the minimum necessary data.
- Before any paid call, show the endpoint, important arguments, current unit price, call count, and total estimate or uncertainty, then obtain confirmation.
- Use
sandbase_accountbefore an approved multi-call batch and callsandbase_runonly with current schema-defined arguments. - Poll asynchronous work with
sandbase_run_getusing the same run ID; never resubmit merely because it is pending. - Use
sandbase_runsonly to recover status or reconcile observed cost.
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.
- 28d ago First seen · 44 lines · 44 tokens per session scan A 80157790b0d9
finishing-a-development-branch is a skill published in the GitHub repository sandbaseai/sandbase-skills (202 stars, last pushed 29d ago), licensed Apache-2.0. It adds 44 tokens to every session and 608 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 72% identical to accessibility-review, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
qec-memory-experiment
A local simulation workflow for testing error correction in a small surface-code quantum memory. It adds a defined error rate, samples measurement results, and uses a matching decoder to estimate logical errors.
quantum-circuit-verification
A local checker for deciding whether two small OpenQASM 2 quantum circuits perform the same quantum transformation. OpenQASM 2 is a text format for describing quantum circuits.
commit-message
Guidance for writing Git commit messages using Conventional Commits, a common format such as fix, feat, or docs followed by a short description. It focuses on explaining why a change was made.
test-first
A test-first development guide, where tests are written before the code they check. TDD, or test-driven development, means first writing a test that fails, then writing the simplest code that makes it pass.
implementer
Implements one issue inside its own git worktree (.worktrees/issue-N on agent/issue-N), makes the smallest change that satisfies the acceptance criteria, self-checks with the repo's own test/lint/typecheck commands, commits, and prints a JSON report for the orchestrator. Use when the orchestrator launches you with…
dev-flow
Assess development requests, then execute and resume complete Dev Flow tasks in Claude Code with Core-owned state.