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 agentmods add commands/azrtydxb/procoder/releasegit clone --depth 1 https://github.com/azrtydxb/procoderWhat 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 | $0.00030 | $0.00519 |
| Opus 5 | $0.00015 | $0.00260 |
| Sonnet 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 2d 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.
- 2d ago First seen · 38 lines · 30 tokens per session scan A aa68ba2aab29
release is a command published in the GitHub repository azrtydxb/procoder (196 stars, last pushed 2d ago), licensed Apache-2.0. It adds 30 tokens to every session and 519 once invoked, about $0.0002 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
setup
Initialize a new project with SDLC-compliant structure. Creates required files, configures build system, sets up CI/CD, and establishes quality tooling.
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.
run-tests
Run automated functional tests using the hook-driven test framework. Execute the test suite to validate all project functionality.
test-report
Generate test execution report in markdown format.
add-test
Interactively add a new test definition to the test suite.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.