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 reidemeister94/development-skills --skill wrap-up-branchgit clone --depth 1 https://github.com/reidemeister94/development-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/reidemeister94/development-skills/wrap-up-branch)<a href="https://agentmods.dev/skills/reidemeister94/development-skills/wrap-up-branch"><img src="https://agentmods.dev/badge/skills/reidemeister94/development-skills/wrap-up-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/reidemeister94/development-skills/wrap-up-branch"><img src="https://agentmods.dev/badge/skills/reidemeister94/development-skills/wrap-up-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.00783 |
| Opus 5.5 | $0.00012 | $0.00313 |
| Sonnet 5.5 | $0.00006 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
wrap-up-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 27d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap up branch
Finish the current feature branch so it can land safely.
Invoking the skill authorizes in-scope edits, their commits on the feature branch, and merging the target into the feature branch.
Merging into the target and pushing wait for the final question.
Run the steps in order. Stop on a failed gate.
Each step that changes files ends with development-skills:commit and the matching Conventional Commit type.
1. Resolve scope
- The feature branch is the current
HEAD. Stop on a detachedHEADor whenHEADis already the target. - The target is
$ARGUMENTS. Without it, inspectdev,develop, anddevelopment; otherwise use the default branch. - Name
mainormasteras protected in the final question. - A dirty working tree needs one decision: commit the listed paths or stop. Never stash without permission.
- Fetch
origin, then usegit diff <merge-base>...HEADas the scope. Keep temporary review files outside the repository. - Run the project's checks as a baseline. Stop if the branch is already red.
- State the target and merge-base before changing the branch.
2. Tests
Invoke development-skills:create-test for the branch scope.
Add missing proof for the branch's behavior and relevant rejection, limit, timeout, retry, permission, concurrency, and partial-failure cases.
Judge proof by failures caught, not counts. A new failing test exposes a defect. Fix it only when the fix stays inside branch scope; otherwise stop and report it. Run focused tests, then project checks.
3. Review and fix
Invoke development-skills:staff-review on the merge-base range.
Provide the plan, issue, or pull request description as the requirement when available.
Fix every MISSING or EXTRA finding and every CRITICAL or HIGH quality finding.
Report MEDIUM and LOW findings unchanged.
Run affected checks and re-review the fix diff. Stop after three failed fix rounds or a conflict with an existing decision.
4. Documentation
Invoke development-skills:align-docs with the branch scope.
When the repository has a CHANGELOG.md, invoke development-skills:changelog in from-commits mode.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 27d ago First seen · 72 lines · 30 tokens per session scan A afa5d77fb674
wrap-up-branch is a skill published in the GitHub repository reidemeister94/development-skills (12 stars, last pushed 26d ago), licensed MIT. It adds 30 tokens to every session and 783 once invoked, about $0.0001 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-09-20.
Other skills, from other repositories
review
Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.
refactor
Refactor existing code by extracting helpers, splitting files, removing duplication, or untangling dependencies. Supports resumable and batch runs. Use for structural changes that preserve behavior; use zuvo:build for new features.
ring:generating-pr-descriptions
Generating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.
ring:creating-worktrees
Creating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing…
mutation-test
Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot…
write-tests
Write tests for existing production code. Processes ONE file at a time through a full pipeline: analyze, inventory (frozen BEFORE writing), write, executable coverage gate, verify, blind coverage audit, adversarial review, log. Uses CodeSift for discovery and analysis when available. Modes: [path] (specific target)…