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 arbiterForge/codeArbiter --skill finishing-a-development-branchgit clone --depth 1 https://github.com/arbiterForge/codeArbiterWrote 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/arbiterforge/codearbiter/finishing-a-development-branch)<a href="https://agentmods.dev/skills/arbiterforge/codearbiter/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/arbiterforge/codearbiter/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/arbiterforge/codearbiter/finishing-a-development-branch"><img src="https://agentmods.dev/badge/skills/arbiterforge/codearbiter/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.00034 | $0.04104 |
| Opus 5.5 | $0.00014 | $0.01642 |
| Sonnet 5.5 | $0.00007 | $0.00821 |
| Haiku 4.5 | $0.00003 | $0.00410 |
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 today.
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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- today Changed · +10 lines 3fd6bc674e95
- 9d ago Changed · -10 lines 81babe5b3561
- 13d ago Changed · +28 lines d121baaeca43
- 18d ago Changed · +29 lines a37f99f3e32f
- 29d ago Changed · +78 lines · -49 tokens per session 6e7eec27319d
- 1mo ago Changed · +20 lines 1b84f309d315
- 1mo ago Changed · +2 lines 2947bde8afa2
- 1mo ago Changed · +21 lines 1bb684d2fc34
- 1mo ago First seen · 92 lines · 83 tokens per session scan A 15cdb1c4a27f
finishing-a-development-branch is a skill published in the GitHub repository arbiterForge/codeArbiter (149 stars, last pushed today), licensed AGPL-3.0. It adds 34 tokens to every session and 4,104 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-03.
Other skills, from other repositories
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.
roadmap-task-deliver
Deliver the first eligible unfinished roadmap task through implementation, review, green CI, PR merge, and a task-status update. Use for autonomous delivery from local roadmap and task files. Files can be outside the code repository or outside Git.
jira-issue-deliver
Autonomously deliver one Jira issue from intake to a ready GitHub pull request. Use only when the user authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback.
plan-deliver
Autonomously deliver an approved implementation plan to a ready GitHub pull request. Use when the user supplies a plan in the conversation or a file and authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback; use jira-issue-deliver when the…
enterprise-pr-review
End-to-end PR conversation closer and advisory review harvester for enterprise work. Use this whenever the user mentions unresolved PR conversations, Copilot/GitHub review comments, a PR that cannot merge, skipped/non-blocking Copilot feedback, a failed PR review, or asks to address/resolve/learn from PR feedback. It…
gh-issues
Use when turning a diagnose.buildpacket.v1 JSON packet, bug diagnosis, or agent handoff into GitHub issues or issue comments, especially when the user wants ready-for-agent work items created without implementing code.