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/init)<a href="https://agentmods.dev/commands/azrtydxb/procoder/init"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/init/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/init"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/init.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.00016 | $0.00408 |
| Opus 5.5 | $0.00006 | $0.00163 |
| Sonnet 5.5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
init 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 29d 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:init.
Use the user's explicit --host <name> (repeatable for additional hosts) or
--all selection when provided. Otherwise the binary uses reliable plugin
context. If it asks which host to set up, ask the user and re-run with their
choice; never assume all hosts or infer one from repository directories.
-
Run:
procoder init $ARGUMENTSIt surveys the repository and prints one install command per missing formatter, chosen for this machine's package managers. It updates only the selected hosts' local gitignore entries, leaving
.procoder/trackable. It also prints the additive.procoder/hosts.jsondeclaration and needed rule copies from the project'sAGENTS.md. Review and write that content to the named paths, preserving existing integrations. If the master is absent, establish the project's shared contract first; do not copy unrelated project instructions. Plugin installation remains host-specific, not an init side effect.--yesexecutes formatter installs, not generated files. -
Execute each printed command yourself, one at a time, so the user sees exactly what is being installed and how. If a command fails, show the error and stop — do not improvise a different installer; the printed command is the supported path.
-
For any line saying "install by hand", relay it to the user — procoder found no package manager it knows on this machine.
-
Finish by running:
procoder doctorand confirm every gap is closed. A tool is installed when doctor says ok — an installer exiting 0 is not the proof; doctor is. Re-run
procoder init $ARGUMENTSwith the same selection to verify the integration content is also current.
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.
- 29d ago Changed · +14 lines c902e059a3fe
- 1mo ago First seen · 28 lines · 16 tokens per session scan A d3982234aee2
init is a command published in the GitHub repository azrtydxb/procoder (211 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 408 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
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…
sm-scour
Run slop-mop's comprehensive pre-PR sweep for this repository.
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-diff
Check two code versions for semantic equivalence — use after a refactor or rewrite.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
review
Review Grok output (diff gate — never auto-commit).