What is manage-rules?

A tool for inspecting and switching project live-rules on or off. Live-rules are project instructions that are injected into coding-agent work.

Use it to list rules, audit active instructions, explain an injected rule, enable or disable rules, and synchronize rule files after changes.

It lets you see which instructions are active and clean up enabled rules without changing what those rules say.

manage-rules — Skill for Claude Code and Codex by Eigenwise: A tool for inspecting and switching project live-rules on…

Install

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.

agentmods

npx agentmods add skills/eigenwise/eigenwise-toolshed/manage-rules

Any agent

npx skills add Eigenwise/eigenwise-toolshed --skill manage-rules

Clone the repo

git clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshed

Made for: Claude Code, Codex.

Or install live-rules, the plugin that ships this one along with the rest of its 2 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/eigenwise/eigenwise-toolshed/manage-rules.svg)](https://agentmods.dev/skills/eigenwise/eigenwise-toolshed/manage-rules)

Your own site

<a href="https://agentmods.dev/skills/eigenwise/eigenwise-toolshed/manage-rules"><img src="https://agentmods.dev/badge/skills/eigenwise/eigenwise-toolshed/manage-rules.svg" alt="Measured on agentmods" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,547 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00036	$0.01547
Opus 5	$0.00018	$0.00773
Sonnet 5	$0.00007	$0.00309
Haiku 4.5	$0.00004	$0.00155

Measured 5d ago against content hash f9dc8c6046bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

manage-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 5d 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.

plugins/live-rules/skills/manage-rules/SKILL.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Manage Rules

Read, audit, and toggle live rules without changing what any rule says. For authoring or editing rule content, use the add-rule skill. The full format is documented in ../add-rule/references/rule-format.md.

For atomic storage, never edit .claude/live-rules/manifest.json. After every rule-file change, run:

node "${CLAUDE_PLUGIN_ROOT}/scripts/sync-atomic-rules.js" --project "${CLAUDE_PROJECT_DIR}"

Find the rules

New workspaces store one rule per Markdown file under .claude/live-rules/rules/; their generated manifest stays beside them. Existing workspaces may still use one Markdown file. Resolve that legacy file in this order:

If LIVE_RULES_PATH is set (commonly in .claude/settings.json under env), that path is the file (project-relative, absolute, or ~-relative).
Otherwise it is .claude/live-rules.md at the project root.

If the file does not exist, there are no rules yet; point the user at add-rule to create the first one.

How to read the files

For atomic storage, inspect every .md rule under .claude/live-rules/rules/. For legacy storage, the file is a sequence of rule sections. Each rule is a frontmatter block between --- fences followed by its body, and the next --- begins the next rule. Anything before the first fence is a title or intro and is ignored. Parse each section's frontmatter to get its scope, priority, and enabled state; the body is the instruction text.

Tasks

List the rules

Parse every section and present a compact table (use the description as the rule's name, falling back to its position in the file):

Rule	Scope	Fires when	Enabled
House style	global	every prompt	yes
React component conventions	glob	editing `*/.tsx`	yes
API layer rules	dir	editing under `packages/api`	yes
Deploy checklist	prompt	prompt matches `deploy`	yes
Strict lint gate	glob	editing `*/.ts`	no

Read the full file on GitHub · 120 lines

Changes

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.

5d ago First seen · 120 lines · 36 tokens per session scan A f9dc8c6046bf

Subscribe to this mod's changes

manage-rules is a skill published in the GitHub repository Eigenwise/eigenwise-toolshed (37 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,547 once invoked, about $0.0002 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-30.

Building agents

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens