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 wazimmerman/zimster --skill finishing-a-development-branchgit clone --depth 1 https://github.com/wazimmerman/zimsterWrote 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/wazimmerman/zimster/finishing-a-development-branch)<a href="https://agentmods.dev/skills/wazimmerman/zimster/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/wazimmerman/zimster/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/wazimmerman/zimster/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/wazimmerman/zimster/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.00030 | $0.00848 |
| Opus 5 | $0.00015 | $0.00424 |
| Sonnet 5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
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 11d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finishing a Development Branch
This workflow always runs at the end of owner-driven development, including no-commit and disposable-repository work.
1. Inspect complete repository state
Run and record:
git rev-parse --show-toplevel
git branch --show-current
git status --short
git diff
git diff --cached
git log --oneline <merge-base>..HEAD
Identify base branch/merge base, linked-worktree state, commits belonging to the
work, unrelated user changes, staged files, unstaged files, and untracked
files. Generate a change-snapshot or read every untracked file; git diff
alone cannot establish readiness for brand-new files.
For every dispatch v2 record, require a consumed authoritative proposal, requested/effective routing accounting, and persistent-owner acceptance. A pending or rejected delegated implementation cannot satisfy completion.
A harness-managed detached checkout may require native branch/handoff controls. Report limitations instead of pretending push/PR capability.
2. Enforce Git disposition
- Existing project on default branch without explicit authorization should not have reached implementation; stop and surface the policy breach.
- On an isolated feature branch/worktree, verified vertical slices should be committed unless the user said not to commit.
- In a disposable/test repo explicitly intended for direct work, default branch and uncommitted output are permitted when that was the chosen policy.
- When the user says “do not commit,” do not stage or commit; report the exact verified but uncommitted files.
- A delegated implementer commit is accepted only from its dedicated branch/worktree and explicit commit grant.
Never leave verified but uncommitted work implicit. State whether it is staged, unstaged, or untracked and what the user must preserve.
3. Verify final code
Load verification-before-completion. Run canonical required gates fresh on the
final tree and record exact test discovery/counts, warnings, ignored/skipped
tests, and external/manual evidence. Re-read the mission line by line.
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.
- 11d ago First seen · 107 lines · 30 tokens per session scan A 7b6a6a6fda84
finishing-a-development-branch is a skill published in the GitHub repository wazimmerman/zimster (2 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 848 once invoked, about $0.0002 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
ship
Enforces Law 1 (Research Before Executing), Law 3 (One Thing at a Time), and Law 4 (Verify Before Reporting) of the 7 Laws of AI Agent Discipline. Fix one defect through TDD and one PR, isolate unrelated dirty checkouts in an owner-locked clean worktree, and return only eligible clean checkouts to the detected default…
code-quality-review
Checklist and method for reviewing code quality — readability, maintainability, SOLID, DRY, performance, and backward compatibility. Use when asked to review code, a diff, a branch, or a merge request for quality, or before finalizing significant changes. For GitHub PR review use the built-in /review; for…
treework
Use TreeWork, a tree-guided development plugin for complex or evolving software projects that need staged alignment, pre-coding technical Specs, declarative project-tree planning, branch-scoped Git worktrees, durable recovery, and protected completion. It teaches the Agent to move through development along the Tree…
repository-bootstrap
Audit and establish or upgrade the canonical repository governance baseline. Use only when explicitly asked to bootstrap, standardize, or upgrade a repository; do not use for feature development or source-code restructuring.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.