Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add juntossomosmais/pommel/plugin install conditional-rules-pluginWrote 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/juntossomosmais/pommel/manage-rules)<a href="https://agentmods.dev/commands/juntossomosmais/pommel/manage-rules"><img src="https://agentmods.dev/badge/commands/juntossomosmais/pommel/manage-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.1 | $0.00017 | $0.00699 |
| Opus 5 | $0.00009 | $0.00349 |
| Sonnet 5 | $0.00003 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade C, and why
manage-rules scanned grade C with 2 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 8d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s https://api.github.com/repos/<owner>/<repo>/releases/latest | python3 -c "import sys, json; print(json.load(sys.stdin)['tag_name'])" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://api.github.com/repos/<owner>/<repo>/releases/latest | python3 -c "import sys, json; print(json.load(sys.stdin)['tag_name'])" How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rules
Classify first, then edit
Conventional (native Claude Code memory) — skip the conditional docs entirely and edit the file:
- the target is any
CLAUDE.md, or any path under.claude/rules/ - the user says "conventional"
Conditional — read ${CLAUDE_PLUGIN_ROOT}/hooks/conditional_rules/CONDITIONAL_RULES.md for predicate / combinator / event mechanics before writing. Not found: ask the user where it lives. Project-level conditional rules live in .claude/conditional_rules/rules.json (always applied for that repo; activation_criteria is ignored there); plugin rule packs keep theirs in rules/rules.json.
Neither is stated and no path gives it away — ask which. For conventional, the claude-code-guide subagent (if available) covers best practices.
Writing a rule
- A rule must state things as imperative (describe what the developer should do) and not as descriptive (describe what the code does).
- Rules should be concise and focused on specific conditions or patterns to enforce.
- Rules should be easily understandable and maintainable by developers.
- Rules should be designed to prevent common mistakes and ensure code quality.
- Rules should be short—very short—and as pragmatic as possible.
- Rules should not reference other rules because they are loaded progressively.
- When a rule content requires an external link, prefer GitHub repositories links.
Pin every citation link
/blob/main/... links rot silently. Pin to a stable ref:
- Semver tags →
/blob/<vX.Y.Z>/path. Find latest:curl -s https://api.github.com/repos/<owner>/<repo>/releases/latest | python3 -c "import sys, json; print(json.load(sys.stdin)['tag_name'])" - Date tags (e.g.
opentelemetry.io) →/blob/<YYYY.MM>/path. Find latest:curl -s 'https://api.github.com/repos/<owner>/<repo>/tags?per_page=5' | python3 -c "import sys, json; print([t['name'] for t in json.load(sys.stdin)])" - Neither → commit SHA. Find latest for a specific file:
curl -s 'https://api.github.com/repos/<owner>/<repo>/commits?path=<filepath>&per_page=1' | python3 -c "import sys, json; print(json.load(sys.stdin)[0]['sha'])"
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.
- 8d ago First seen · 50 lines · 17 tokens per session scan C 1e9a3c2dd139
manage-rules is a command published in the GitHub repository juntossomosmais/pommel (5 stars, last pushed 20d ago), licensed MIT. It adds 17 tokens to every session and 699 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
patterns
List makoto's integrity pattern catalog (read-only).
issue-plan-review
Read a GitHub issue and all comments, review the implementation plan, independently assess each finding, and present findings.
issue-plan
Read a GitHub issue, analyze the codebase, and create a staged implementation plan.
fable-eval
Run the fable-mode eval suite (probes → pairwise judge → report). Costs tokens — runs headless claude many times. Optional arg: a probe id substring to filter.
pr-create
Create a pull request for the current branch with structured description.
push
Commit, push, and post a progress comment using session context or branch detection.