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 Vimalk0703/shipworthy --skill finishing-a-development-branchgit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/finishing-a-development-branch)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/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/vimalk0703/shipworthy/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/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.00430 |
| Opus 5 | $0.00015 | $0.00215 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
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 10d 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
The 5-Step Completion Workflow
Step 1: Verify Everything Passes
Before any merge activity:
- Run the full test suite — ALL tests must pass
- Run the build — zero errors
- Run the linter — zero errors
- This is non-negotiable. Do NOT skip to step 2 with failing tests.
Step 2: Determine the Base Branch
- Check what branch this was branched from
- Usually
mainordevelop - Verify the base branch is up to date:
git fetch origin - Check for conflicts:
git diff main...HEAD
Step 3: Present Options
Tell the user their options:
- Merge commit:
git merge --no-ff(preserves branch history) - Squash merge:
git merge --squash(clean single commit) - Rebase and merge:
git rebase mainthen fast-forward merge - Create PR: push and create a pull request for review
Recommend based on:
- Single logical change → squash
- Multiple meaningful commits → merge commit
- Needs review → PR
Step 4: Execute
Carry out the user's chosen strategy. If creating a PR, use gh pr create with a clear title and description.
Step 5: Clean Up
After successful merge:
- Delete the local branch:
git branch -d feature/branch-name - Delete the remote branch (if applicable):
git push origin --delete feature/branch-name - Remove worktree (if used):
git worktree remove .worktrees/branch-name - Verify main is clean:
git checkout main && git pull && npm test
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.
- 10d ago First seen · 45 lines · 30 tokens per session scan A 81c8dbbd4ea6
finishing-a-development-branch is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 430 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
conventional-commits
Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward…
hedgehog-contributing
Use when the user wants to contribute a fix or roadmap item back to the Hedgehog project itself (skyf0xx/hedgehog) rather than their own project. Triggers on "let's fix that in Hedgehog", "I want to contribute", "let's pick up a roadmap item", or when tweaker offers this at the end of a build and the user says yes.…
pr-writing
Use whenever writing a PR title/description, a commit message body, a code review comment, or an issue — in Hedgehog's own repo or any consuming project. Triggers on "open a PR", "write the PR description", "comment on this PR", "file an issue". Covers writing style (terse, info-dense, Simplified Technical English)…
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…
team-release
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.