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/juntossomosmais/pommelWrote 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/plugins/juntossomosmais/pommel/conditional-rules-plugin)<a href="https://agentmods.dev/plugins/juntossomosmais/pommel/conditional-rules-plugin"><img src="https://agentmods.dev/badge/plugins/juntossomosmais/pommel/conditional-rules-plugin/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/plugins/juntossomosmais/pommel/conditional-rules-plugin"><img src="https://agentmods.dev/badge/plugins/juntossomosmais/pommel/conditional-rules-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
conditional-rules-plugin 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
{
"name": "conditional-rules-plugin",
"description": "A plugin-scoped replacement for Claude Code's native nested-`CLAUDE.md` rules.",
"version": "0.1.0",
"author": { "name": "Juntos Somos Mais", "url": "https://github.com/juntossomosmais" },
"homepage": "https://github.com/juntossomosmais/pommel/blob/main/plugins/conditional-rules-plugin/hooks/conditional_rules/CONDITIONAL_RULES.md",
"repository": "https://github.com/juntossomosmais/pommel",
"license": "MIT",
"keywords": ["rules", "hooks", "context-engineering", "conditional-loading"]
}
What it installs
The manifest is a name and a version. 1 command, 3 hooks travel with it, and installing the plugin installs all of them — 17 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 11 lines scan A 0a06e981e04d
conditional-rules-plugin is a plugin published in the GitHub repository juntossomosmais/pommel (5 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
handoff
Portable project memory + development workflow for coding agents: auto-loads STATUS+RULES each session, enforces folder-level CONTEXT.md on edit, nudges durable state updates at turn end, scaffolds the system into any repo via guided discovery, and ships a tiered 6-phase workflow skill set covering every phase (brief.
amber
Zero-dependency context survival kit for Claude Code. Auto-checkpoints your session state to plain Markdown before compaction, restores it after — plus focus skills that keep Claude lean and on-task. No database, no background process, no AI compression. Just files you can read.
hush
Quieter sessions for Claude Code: less narration, shorter tool output and concise answers focused on the result.
razor
Reuse-first checks for Claude Code: reconsider dependencies, file growth and unnecessary code before adding more.
token-master
Token-efficient code-understanding harness. Routes structural questions (callers, callees, impact, inheritors) to a prebuilt code graph instead of repeated grep and file-reads, cutting cumulative context tokens. Type /token-master in a repo to build the index and turn on routing.
trove
Repository memory for Claude Code: index symbols and architecture, progressively retrieve context beyond the context window, and capture durable engineering decisions in a personal trove.