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 aigentive/RalphX/plugin install ralphxWrote 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/skills/aigentive/ralphx/rule-manager)<a href="https://agentmods.dev/skills/aigentive/ralphx/rule-manager"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/rule-manager/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/skills/aigentive/ralphx/rule-manager"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/rule-manager.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.00070 | $0.00774 |
| Opus 5.5 | $0.00028 | $0.00310 |
| Sonnet 5.5 | $0.00014 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
rule-manager 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule Manager
Iteratively optimizes .claude/rules/ for token efficiency. Each run: audit -> pick ONE optimization -> apply -> log.
Step 1: Read Framework Reference
Read the memory framework doc for context on priorities and standards:
${CLAUDE_PLUGIN_ROOT}/memory-framework.md
Also fetch/refresh the official Claude Code memory docs (cached locally):
"${CLAUDE_PLUGIN_ROOT}/skills/rule-manager/scripts/rule-fetch-docs.sh"
Step 2: Audit
Run the audit script to collect current state:
"${CLAUDE_PLUGIN_ROOT}/skills/rule-manager/scripts/rule-audit.sh" --json
Parse the JSON output. Report to user:
- Total files, lines, estimated tokens
- Files with/without paths: frontmatter
- Files with @ references
- Health indicators (oversized, unscoped, refs)
Also read the optimization log to see what's been done (per-day files):
.claude/memory/ (read the latest file, or all files for full history)
Step 3: Identify ONE Optimization
Pick the HIGHEST priority that applies (do NOT do multiple):
Priority 1: @ References Between Rules
If any rule file has @ references to other rule files:
"${CLAUDE_PLUGIN_ROOT}/skills/rule-manager/scripts/rule-strip-refs.sh" <filename> --dry-run
Show the preview to user. If approved:
"${CLAUDE_PLUGIN_ROOT}/skills/rule-manager/scripts/rule-strip-refs.sh" <filename>
Priority 2: Unscoped Domain Rule
If a rule lacks paths: frontmatter but is domain-specific:
"${CLAUDE_PLUGIN_ROOT}/skills/rule-manager/scripts/rule-suggest-paths.sh" <filename>
Review the suggestions. For complex cases, use an Explore agent to grep the codebase for the rule's key terms. Show proposal to user. If approved:
"${CLAUDE_PLUGIN_ROOT}/skills/rule-manager/scripts/rule-apply-paths.sh" <filename> "pattern1" "pattern2"
Priority 3: Oversized Rule (>400 LOC)
If a rule exceeds 400 lines:
- Read the file and identify distinct sections
- Propose splitting into 2-3 focused files with paths: frontmatter
- Create new files, delete original
- This is a manual operation (no script -- requires judgment)
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- scripts/lib/common.sh 1.9 KB runs code
- scripts/rule-apply-paths.sh 1.6 KB runs code
- scripts/rule-audit.sh 4.2 KB runs code
- scripts/rule-deps.sh 2.3 KB runs code
- scripts/rule-fetch-docs.sh 1.8 KB runs code
- scripts/rule-find-orphans.sh 1.9 KB runs code
- scripts/rule-log.sh 705 B runs code
- scripts/rule-stats.sh 1.3 KB runs code
- scripts/rule-strip-refs.sh 1.1 KB runs code
- scripts/rule-suggest-paths.sh 2.1 KB runs code
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 · 99 lines · 70 tokens per session scan A 75a17e8d84b3
rule-manager is a skill published in the GitHub repository aigentive/RalphX (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 70 tokens to every session and 774 once invoked, about $0.0003 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-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.