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/azrtydxb/procoderWrote 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/azrtydxb/procoder/release)<a href="https://agentmods.dev/commands/azrtydxb/procoder/release"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/release/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/azrtydxb/procoder/release"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/release.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.00519 |
| Opus 5.5 | $0.00012 | $0.00208 |
| Sonnet 5.5 | $0.00006 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
release 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 1mo 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
The user invoked /procoder:release with arguments: $ARGUMENTS
The command below is the procoder binary on PATH.
- Run
procoder release <version>(or bareprocoder releaseto check the newest changelog version). The controller verifies in one pass: every file in[release] filescarries the version, the changelog has its entry, the working tree is clean, the gate is clean, and the suite is green under [test] policy. - Before the first fix, run /procoder:simplify over the whole repo
(
repo): take the cuts you agree with, say why not for the rest. - Rebuild the committed binaries with
scripts/build-dist.shwhenever this release changes the binary. It writesdist/anddist/SHA256SUMStogether, which is the point: the workflow publishes that file beside the assets,self-upgradeverifies every download against it, and a release whose checksums describe the previous build is one nobody can upgrade to. A test compares the file against the committed binaries, so a hand-builtdist/goes red before the tag. - Fix everything the release controller listed — bump the files, write
the changelog entry, commit — then rerun
procoder releaseuntil it answers ready. The entry's layout is not free-form: CHANGELOG.md opens with the template, and the release job publishes the entry verbatim as the GitHub Release notes, so what you write there is what someone downloading the binary reads. A one-sentence italic summary first, then headlines that open with their kind — Added, Fixed, Changed, Removed, Security — each linking its issue, worst breakage first. A test over the newest entry holds the shape. - When the release controller answers ready it prints the tag command; run that command yourself and push the tag. The binary never tags (P-CONTROL).
- A repo without
[release] filesin .procoder/config.toml gets an honest "verified nothing" on the version-sync leg — set the list so the check has teeth.
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.
- 1mo ago First seen · 38 lines · 30 tokens per session scan A aa68ba2aab29
release is a command published in the GitHub repository azrtydxb/procoder (211 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 519 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-08-30.
Other commands, from other repositories
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
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.
worktree
Manage git worktrees for isolated feature development.
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
review
Fast review of staged changes. Critical findings only — no style nits.