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.
npx agentmods add commands/cukas/patrol/patrol-rulesgit clone --depth 1 https://github.com/cukas/patrolWrote 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/cukas/patrol/patrol-rules)<a href="https://agentmods.dev/commands/cukas/patrol/patrol-rules"><img src="https://agentmods.dev/badge/commands/cukas/patrol/patrol-rules.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00390 |
| Opus 5 | $0.00006 | $0.00195 |
| Sonnet 5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
patrol-rules 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 4d 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
/patrol-rules
List all active rules with their source, level, and status.
When invoked with no arguments
Read the cached rules from /tmp/patrol-{session_id}/rules.json.
Present as a table:
| # | Rule | Level | Source | Status |
|---|---|---|---|---|
| 1 | test-before-push | warn | .patrol/rules.json | active |
| 2 | read-before-edit | warn | built-in | active |
| 3 | no-force-push-main | block | built-in (safety) | active |
Group by category: Safety → Workflow → Quality → Architecture → Custom
For each rule, determine source:
- IDs starting with
_safety-→ "built-in (safety)" - IDs matching built-in investigation rules (read-before-edit, investigate-first, test-after-changes) → "built-in"
- All others → the file path they were loaded from (show as relative path)
When invoked with explain <rule-id>
Show full rule details:
- ID, name, category, level
- Trigger type and match pattern
- Require conditions (if any)
- Message template
- Source file
- Tags (if any)
When invoked with add <template-id>
Show available built-in rule templates that are not currently active.
If a specific template-id is given, add it to ~/.patrol/my-rules.json.
When invoked with disable <rule-id>
Disable a personal rule by setting "enabled": false in ~/.patrol/my-rules.json.
Cannot disable repo or company rules — inform the user that they need to modify the source file.
Cannot disable safety rules — inform the user that safety rules are always active.
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.
- 4d ago First seen · 48 lines · 13 tokens per session scan A 138f730910c4
patrol-rules is a command published in the GitHub repository cukas/patrol (3 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 390 once invoked, about $0.0001 per session on Opus 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-31.
Other commands, from other repositories
sm-sail
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.
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-wake-angry-drunk-captain
The last-resort verb. Use it ONLY when the loop is genuinely exhausted: barnacles filed, gates green or truly unfixable, and the single remaining move is a human judgment call no sm verb can make for you.
sm-barnacle
Use when sm itself gives invalid guidance, blocks valid work, produces confusing output, or breaks install/upgrade/refit flow. Do not use this for real target-repo failures; fix those through the normal rail.
sm-init
Run when you find a repo with sm installed but no .sbconfig.json — or after upgrading slopmop to pick up new gates.
sm-refit
Run slop-mop's one-time onboarding remediation rail for this repository.