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/jeremydev87/codingbuddy/finishing-a-development-branchnpx skills add JeremyDev87/codingbuddy --skill finishing-a-development-branchgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWrote 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/jeremydev87/codingbuddy/finishing-a-development-branch)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/finishing-a-development-branch.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.00029 | $0.02128 |
| Opus 5 | $0.00015 | $0.01064 |
| Sonnet 5 | $0.00006 | $0.00426 |
| Haiku 4.5 | $0.00003 | $0.00213 |
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 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finishing a Development Branch
Overview
Guide the completion of development work on a branch — decide how to integrate, verify readiness, execute the choice, and clean up.
Core principle: Verify before you ship. Present options, don't assume. Clean up after yourself.
The Iron Law
NO MERGE WITHOUT GREEN TESTS AND CLEAN STATUS
If tests fail or uncommitted changes exist, STOP. Fix first. No exceptions.
Corollary: Never push directly to main/master. Always use a PR for protected branches.
When to Use
- Implementation is complete on a feature branch
- All planned tasks are done (or intentionally deferred)
- Ready to integrate work back to base branch
- Need to decide: merge, PR, or abandon
- End of an executing-plans or subagent-driven-development session
- Wrapping up work in a git worktree
When NOT to Use
- Work is still in progress (keep working)
- You haven't run tests yet (run them first)
- You're on the main/master branch (nothing to finish)
Phase 1: Pre-Completion Checklist
MANDATORY. Complete every item before proceeding.
Must Pass (blocking)
# 1. All tests pass
npm test # or: yarn test, pytest, go test ./...
# 2. No type errors
npx tsc --noEmit # or equivalent for your language
# 3. No uncommitted changes
git status # must be clean
# 4. Branch is up to date with base
git fetch origin
git merge-base --is-ancestor origin/<base> HEAD # exit 0 = up to date
- All tests pass (zero failures)
- No type errors (
tsc --noEmitor equivalent) - Working directory clean (
git statusshows nothing) - No untracked files that should be committed
- Branch is up to date with base branch
Should Check (non-blocking)
- Linting passes (eslint/prettier or equivalent)
- No TODO/FIXME left in new code
- Commits are logically grouped (not a mess of WIP)
- Commit messages follow project conventions
Context-Dependent
- If in worktree: confirmed correct worktree
- If linked to issue: issue number in branch name or commits
- If PR already exists: PR is up to date with latest commits
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 · 282 lines · 29 tokens per session scan A 9f50d552ea0e
finishing-a-development-branch is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 2,128 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-30.
Other skills, from other repositories
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:instrumenting-streaming-events
Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…
ring:planning-codebase-simplification
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…