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 yinqd3/workbuddy-skills --skill finishing-a-development-branchgit clone --depth 1 https://github.com/yinqd3/workbuddy-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/yinqd3/workbuddy-skills/finishing-a-development-branch)<a href="https://agentmods.dev/skills/yinqd3/workbuddy-skills/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/yinqd3/workbuddy-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/yinqd3/workbuddy-skills/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/yinqd3/workbuddy-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.00067 | $0.00564 |
| Opus 5.5 | $0.00027 | $0.00226 |
| Sonnet 5.5 | $0.00013 | $0.00113 |
| Haiku 4.5 | $0.00007 | $0.00056 |
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 1mo 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.
What it actually says
完成开发分支
步骤 1：验证测试
运行项目测试套件。测试失败 → 停止，不能继续。
# Python
pytest -q
# Node/TS
pnpm test
如果失败，必须先用 systematic-debugging 修复。
步骤 2：确定基准分支
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
git branch --show-current
步骤 3：呈现四个选项
实现完成。你想怎么做？
1. 合并回 <基准分支>（本地）
2. 推送并创建 Pull Request
3. 保留分支现状（我稍后处理）
4. 丢弃这些工作
选哪个？
步骤 4：执行选择
选项 1：本地合并
git checkout <基准分支>
git pull
git merge <特性分支>
# 运行测试
git branch -d <特性分支>
选项 2：推送 + PR
git push -u origin <特性分支>
gh pr create --title "<标题>" --body "## 概要
- <要点1>
- <要点2>
## 测试计划
- [ ] <验证步骤>"
选项 3：保留现状
报告："保留分支 <名称>。稍后可以继续。"
选项 4：丢弃
先确认：
这将永久删除:
- 分支 <名称>
- 自 <基准分支> 以来的所有提交
输入"discard"确认。
等待精确输入 "discard" 后再执行：
git checkout <基准分支>
git branch -D <特性分支>
常见错误
- 提供选项前不验证测试 → 总是先验证
- 合并不拉取最新基准 → 总是先
git pull - PR 未合并就删分支 → 等待合并确认
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.
- 1mo ago First seen · 93 lines · 67 tokens per session scan A b7eb4b8bb4d4
finishing-a-development-branch is a skill published in the GitHub repository yinqd3/workbuddy-skills (15 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 564 once invoked, about $0.0003 per session on Opus 5.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
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
om-auto-continue-pr-loop
Advanced om-auto-continue-pr for PRs started by om-auto-create-pr-loop — claims the PR, resumes from the first non-done PLAN.md Tasks row in an isolated worktree, keeps the per-step commit and checkpoint discipline (integration tests + screenshots for UI), runs the full gate at completion, keeps spec-only design PRs…
om-auto-update-changelog
Draft a CHANGELOG.md release entry in an emoji-driven format for every PR merged since the last release, then delegate to om-auto-create-pr so it lands as a docs PR against the configured base branch. Honors the Supersede Credit Rule and verifies every credit against commit authorship, so carry-forwards and umbrella…