Borrowing it
Nothing to install: this file belongs to alfredoperez/speckit-companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alfredoperez/speckit-companion/main/.claude/commands/release-loop.mdgit clone --depth 1 https://github.com/alfredoperez/speckit-companionWrote 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/alfredoperez/speckit-companion/release-loop)<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/release-loop"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/release-loop/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/alfredoperez/speckit-companion/release-loop"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/release-loop.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.00059 | $0.01082 |
| Opus 5.5 | $0.00024 | $0.00433 |
| Sonnet 5.5 | $0.00012 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
release-loop 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 16d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release loop
The loop stops twice and nowhere else: at step 4, to ask every open decision in one round, and at step 7, for the user to approve the release report. Everything else runs unattended. The agreed design is the canvas at ~/dev/GitHub/obsidian-vault/Projects/speckit companion/Release Loop.canvas.
This command only sequences. Each step's rules live in the command it calls. Create one task per step (TaskCreate) so progress shows.
1. Pick
Triage the open issues (gh issue list), or take the numbers in $ARGUMENTS. Verify each still reproduces on main and close the ones that don't, with the evidence. Form the batch and mark each ticket full or light: full (/speckit-companion-auto) by default, light only for a mechanical fix such as a regex, a doc or a manifest.
2. Fix
Run /fix-tickets with the batch's issue numbers, so it does not stop to confirm the queue. Full tickets run the full loop sequentially, one at a time; light tickets go in a separate --light run. Anything already built by hand goes through /ship-ticket. Merge a PR only after every CI check has finished and passed, never with a check still pending. Nothing is desktop-tested per ticket. Every merged change a user will meet has an entry under ## [Unreleased]; write a missing one with /changelog-entry.
3. QA
Once the batch is merged, run /release-qa on the fresh main: the automated gates, the terminal run, the scripted real-window checks (viewer, navigation, builder, themes, graded by grade-scripted.py), the headless canvas checks, then qa-stage.sh until it prints READY. Hand the user the short click-only Claude Desktop handoff path to paste (first open, stock and two roots, the timed run, the GitHub Copilot app), and turn Desktop's reply into the QA report. A FAIL with an obvious fix goes back to step 2; one that needs a call becomes a step 4 question.
4. Decide (stop)
Collect every decision the fixes and QA raised and ask them all in one round with AskUserQuestion, your recommendation as the first option of each. Never ask whether to release here; that question belongs to step 7.
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.
- 16d ago Changed 5ab22785d407
- 19d ago Changed 34c70b2ee970
- 21d ago Changed · +1 tokens per session 7d03ff0df2df
- 23d ago First seen · 54 lines · 58 tokens per session scan A c733142b3c7b
release-loop is a command published in the GitHub repository alfredoperez/speckit-companion (99 stars, last pushed 6d ago), licensed MIT. It adds 59 tokens to every session and 1,082 once invoked, about $0.0002 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-10-02.
Other commands, from other repositories
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.
4-close-project
Name: 4-close-project Purpose: Apply an OpenSpec change through TDD, verify it, prepare or update the PR, and leave archive for after merge.
release-check
Run the release-readiness umbrella + draft a tweet-length announcement.
repo-sprint
Collection health triage and work-session kickoff (dirty, unpushed, active, release candidates, audit gaps, stale, unpublished).
run-release
Orchestrate a tagged release using the release workflow.