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 strigov/superpowers-strigov-ver --skill finishing-a-development-branchgit clone --depth 1 https://github.com/strigov/superpowers-strigov-verWrote 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/strigov/superpowers-strigov-ver/finishing-a-development-branch)<a href="https://agentmods.dev/skills/strigov/superpowers-strigov-ver/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/strigov/superpowers-strigov-ver/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/strigov/superpowers-strigov-ver/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/strigov/superpowers-strigov-ver/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.06952 |
| Opus 5 | $0.00022 | $0.03476 |
| Sonnet 5 | $0.00009 | $0.01390 |
| Haiku 4.5 | $0.00004 | $0.00695 |
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 — 553 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finishing a Development Branch
Overview
Guide completion of development work by presenting clear options and handling chosen workflow.
Core principle: Verify tests → Detect environment → Present options → Execute choice → Clean up.
Announce at start: "I'm using the finishing-a-development-branch skill to complete this work."
The Process
Step 1: Verify Tests
Before presenting options, verify tests pass:
# Run project's test suite
npm test / cargo test / pytest / go test ./...
If tests fail:
Tests failing (<N> failures). Must fix before completing:
[Show failures]
Cannot proceed with merge/PR until tests pass.
Stop. Don't proceed to Step 2.
If tests pass: Continue to Step 2.
Step 2: Detect Environment
Determine workspace state before presenting options:
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
FEATURE_BRANCH=$(git branch --show-current) # FEATURE_BRANCH is "" in detached HEAD
This determines which menu to show and how cleanup works:
| State | Menu | Cleanup |
|---|---|---|
GIT_DIR == GIT_COMMON, named branch |
Standard 4 options | No worktree to clean up |
GIT_DIR == GIT_COMMON, detached HEAD |
Reduced 3 options (no merge) | Normal repo detached-HEAD flow: push as new branch, keep, or discard; no branch delete unless a branch is created |
GIT_DIR != GIT_COMMON, named branch |
Standard 4 options | Provenance-based (see Step 6) |
GIT_DIR != GIT_COMMON, detached HEAD, provenance-owned |
Reduced 3 options (no merge) | Inline git worktree remove --force (Option 4a provenance subcase) |
GIT_DIR != GIT_COMMON, detached HEAD, harness-owned |
Reduced 3 options (no merge) | Native exit tool only; if unavailable/fails, report failure + manual command (Option 4a harness subcase) |
If FEATURE_BRANCH is empty, the workspace is detached HEAD even in a normal repo. Route to the detached-HEAD 3-option menu before any standard 4-option branch workflow; the 4-option workflow assumes a named branch exists for merge/delete.
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 · 553 lines · 44 tokens per session scan A 6c99b7b5cfd5
finishing-a-development-branch is a skill published in the GitHub repository strigov/superpowers-strigov-ver (4 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 6,952 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".