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 brunob54/superpowers-orchestrator --skill finishing-a-development-branchgit clone --depth 1 https://github.com/brunob54/superpowers-orchestratorWrote 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/brunob54/superpowers-orchestrator/finishing-a-development-branch)<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/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/brunob54/superpowers-orchestrator/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/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.00094 | $0.00534 |
| Opus 5 | $0.00047 | $0.00267 |
| Sonnet 5 | $0.00019 | $0.00107 |
| Haiku 4.5 | $0.00009 | $0.00053 |
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.
What it actually says
Finishing a Development Branch
Close development work with explicit integration choice.
Step 1: Verify
Run full project verification before offering options.
If verification fails, stop and return to implementation.
Step 2: Identify Base Branch
Detect merge base (main/master or repo default) and confirm if unclear.
Step 3: Offer Exactly Four Options
- Merge back to
<base-branch>locally - Push branch and open PR
- Keep branch/worktree as-is
- Discard branch/worktree
Step 4: Execute Safely
Option 1
- Checkout base
- Pull latest
- Merge feature branch
- Re-run verification
- Delete merged branch
- Remove worktree
Option 2
- Push feature branch
- Create PR with a description that includes:
- What changed — one-paragraph summary of the change set
- Why — the motivation or problem this solves (link to plan doc if one exists)
- How to verify — exact commands or steps a reviewer can run to confirm the change works
- Notable decisions — any trade-offs made, alternatives rejected, or non-obvious choices.
If
session-log.mdhas[saved]entries written during this branch's lifetime, extract the Decisions and Rejected bullets from the most recent entry and include them here. This ensures PR reviewers see the "why" without needing to read the log.
- Keep worktree by default (remove only if user asks)
Option 3
- Keep branch and worktree
- Report exact path and branch name
Option 4
- Show destructive impact summary
- Require exact confirmation:
discard - Delete branch and remove worktree
Hard Rules
- Never merge with failing tests.
- Never delete work without explicit confirmation.
- Never force-push unless explicitly requested.
Final Report
Include:
- Selected option
- Commands executed
- Final branch/worktree status
- PR link (if created)
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 · 75 lines · 94 tokens per session scan A 47bfaef1b7e8
finishing-a-development-branch is a skill published in the GitHub repository brunob54/superpowers-orchestrator (3 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 534 once invoked, about $0.0005 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
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
ops-release
OPS on-demand: This skill should be used when the user asks to "release the plugin", "publish ops…