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/simplify)<a href="https://agentmods.dev/commands/azrtydxb/procoder/simplify"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/simplify/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/simplify"><img src="https://agentmods.dev/badge/commands/azrtydxb/procoder/simplify.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.00039 | $0.00501 |
| Opus 5.5 | $0.00016 | $0.00200 |
| Sonnet 5.5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
simplify 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:simplify with arguments:
The command below is the procoder binary on PATH.
This review hunts one thing only: code that should not exist. Correctness
bugs, security, performance — out of scope here; those belong to
procoder check, security, and /procoder:debug.
Scope: with no arguments, review the working-tree diff (git diff plus
staged). With repo (or a path) in the arguments, sweep that whole scope
— use procoder index unused and procoder maintain as starting
evidence, then read.
The diff pass runs before every pull request; the repo sweep before a tag.
Every finding is one line, with a mandatory replacement — a finding without a replacement is hedging, not reviewing:
<file>:L<line>: <tag> <what>. <replacement>.
The five tags:
delete:dead code, unused flexibility, speculative feature. Replacement: nothing.stdlib:hand-rolled code the standard library ships. Name the function.native:a dependency or code doing what the platform already does (CSS over JS, a DB constraint over app code). Name the feature.yagni:an abstraction with one implementation, config nobody sets, a layer with one caller.shrink:same logic, fewer lines. Show the shorter form.
End with the score line: net: -<N> lines possible. — and when there is
genuinely nothing to cut, say exactly Lean already. Ship. and stop;
never invent findings to look thorough.
Rules:
- Never flag a lone smoke test or assert-based self-check as bloat — the minimum check is part of the code, not decoration (see /procoder:tdd).
- A deliberate simplification marked with the debt marker (see
procoder debt) is a recorded decision, not a finding — unless its revisit trigger has arrived. - List the cuts; do not apply them. The user (or the task at hand) decides — P-CONTROL applies to reviews too.
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 · 50 lines · 39 tokens per session scan A 78eb0d52a63b
simplify is a command published in the GitHub repository azrtydxb/procoder (211 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 501 once invoked, about $0.0002 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).