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/status)<a href="https://agentmods.dev/commands/azrtydxb/procoder/status"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/status/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/status"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/status.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.00023 | $0.00175 |
| Opus 5.5 | $0.00009 | $0.00070 |
| Sonnet 5.5 | $0.00005 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
status 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:status.
Run:
procoder status
Every line is a computed fact, not a guess — and a fact that could not be read says so rather than defaulting to something comfortable. Read it before deciding what to do next: the active sprint and its open stories are the committed work, open todo tasks are the standalone list, and a stale index means line numbers cannot be trusted until you rebuild.
The same block is injected at session start, so a resumed session opens
knowing where the project stands. .procoder/state/handoff.md holds
the last session's version of it, plus any notes the previous session
left under its Notes heading.
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 · 23 tokens per session scan A e4ad300a1e2c
status is a command published in the GitHub repository azrtydxb/procoder (211 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 175 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
buddy
Show project status, recommended agents, and next actions — your coding buddy at a glance.
setup-prd
Set up development environment (branch + worktree) for PRD.
sync-github
Sync PRD with GitHub Issues (bidirectional).
lifecycle
Complete milestone lifecycle: audit, archive, and next version.
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
worktree
Manage git worktrees for isolated feature development.