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.
git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductorWrote 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/commands/ibrahim-3d/orchestrator-supaconductor/finishing-a-development-branch)<a href="https://agentmods.dev/commands/ibrahim-3d/orchestrator-supaconductor/finishing-a-development-branch"><img src="https://agentmods.dev/badge/commands/ibrahim-3d/orchestrator-supaconductor/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/commands/ibrahim-3d/orchestrator-supaconductor/finishing-a-development-branch"><img src="https://agentmods.dev/badge/commands/ibrahim-3d/orchestrator-supaconductor/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.00019 | $0.00062 |
| Opus 5 | $0.00010 | $0.00031 |
| Sonnet 5 | $0.00004 | $0.00012 |
| Haiku 4.5 | $0.00002 | $0.00006 |
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.
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.
- 10d ago First seen · 9 lines · 19 tokens per session scan A aa9d50df4c80
finishing-a-development-branch is a command published in the GitHub repository Ibrahim-3d/orchestrator-supaconductor (377 stars, last pushed 5mo ago), licensed AGPL-3.0. It adds 19 tokens to every session and 62 once invoked, about $0.0001 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-30.
Other commands, from other repositories
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
release
Release a new version. Bumps version, updates docs/site/changelog, tags, pushes, and updates the marketplace repo.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.
release
Invoke Eva (Release) to cut a versioned GitHub Release from main, or backfill historical releases. Routes the version-bump commit through a PR (branch protection-friendly) and uses full 40-char SHAs with gh release create to avoid the silent short-SHA rejection.
ship
Ship workflow — detect base branch, merge, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
document-release
Post-ship documentation update — reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped.