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/git)<a href="https://agentmods.dev/commands/azrtydxb/procoder/git"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/git/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/git"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/git.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.00220 |
| Opus 5.5 | $0.00008 | $0.00088 |
| Sonnet 5.5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
git 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:git.
Run:
procoder git
Read the whole report and act on it:
- BLOCK lines are yours to fix before the work is finished: remove conflict markers, unstage junk files, deal with oversized files, amend any commit message carrying an AI-attribution line (the work is the author's — never add Co-Authored-By or "generated with" lines, here or anywhere).
- info lines are judgment calls: address them or explain to the user why not.
- If a template is missing, run
procoder templates, review the printed content, write the files under .procoder/github/, and register the commit template with the printed git config command. - Working on the default branch is information by default; if the user's flow is branch-based, offer to create a branch.
Finish by re-running the command and showing the user the clean report.
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 · 25 lines · 20 tokens per session scan A cd2da105634c
git is a command published in the GitHub repository azrtydxb/procoder (211 stars, last pushed 4d ago), licensed Apache-2.0. It adds 20 tokens to every session and 220 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
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
gh-review-fix-loop
Fix and resolve GitHub PR review threads.
codex-review-waive
Waive a disputed Codex review finding so it stops blocking commits.
gate
The consensus gate — opt this repo in (or out) of duet-signed commits.
diff-review
Generate a visual HTML diff review — before/after architecture comparison with code review analysis.