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/test)<a href="https://agentmods.dev/commands/azrtydxb/procoder/test"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/test/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/test"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/test.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.00020 | $0.00276 |
| Opus 5.5 | $0.00008 | $0.00110 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
test 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:test with arguments: $ARGUMENTS
The command below is the procoder binary on PATH.
- Run
procoder test(add--coveragefor the percentage where the runner measures it natively; pass paths to narrow Go packages and pytest targets). Every detected ecosystem runs: go test, cargo test, the package.json test script, pytest, gradle/maven. - Read the verdicts as given:
okpassed,FAILnames what broke — fix the code or the test, never delete the assertion to get green.----means NOT run (no runner, no test script): that is a gap, not a pass — say so when reporting. - Exit codes: 0 all green, 1 something failed, 2 nothing could run.
- With
[test] policy = "block"in .procoder/config.toml, todo close and backlog story close run this suite and refuse while it is red — the suite being green is part of "done", not a separate favor. - Re-run after every fix; report the final verdict lines to the user.
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 · 22 lines · 20 tokens per session scan A d234d529f277
test is a command published in the GitHub repository azrtydxb/procoder (211 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 276 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
octo-deliver
Delivery phase - Review, validate, and test with multi-AI quality assurance.
ia-verify
Run pre-PR verification chain: build, types, lint, tests, security scan, diff review.
ia-test-browser
Run browser tests on pages affected by current PR or branch.
develop
Implement skill development issues with TDD-governed workflow.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
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…