rules

A command that lists the persistent instructions currently active for a project or workspace. It can show rules from global, project, or technology-specific scopes.

In plain words
What is it for?
Use it after /rules or related requests to inspect rule text, enforcement patterns, detected technology, and totals.
Why use it?
It removes the need to remember which instructions are active or where they came from.

Skill for Claude CodeCodex

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/lexxes-projects/obey/rules
Any agent
npx skills add Lexxes-Projects/obey --skill rules
Clone the repo
git clone --depth 1 https://github.com/Lexxes-Projects/obey

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 388 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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00388
Opus 5 $0.00019 $0.00194
Sonnet 5 $0.00008 $0.00078
Haiku 4.5 $0.00004 $0.00039

Measured yesterday against content hash 717a909f99da, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

skills/rules/SKILL.md · 53 lines

What it actually says

/rules — Show Active Rules

Show the user their active rules.

Process

Run the list script:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/rules-list.sh --filter "all"

If $ARGUMENTS contains --global, --local, --project, or --stack, pass that as the filter instead of "all".

Format the Output

Present the rules as a clean, organized list grouped by scope:

# Active Rules

## Global (apply to all projects)
  1. [ID] [hook+instruction] Never push to main
     → Blocks: git push.*main
  2. [ID] [instruction] Always explain reasoning before writing code

## Stack: rust (apply to all Rust projects)
  3. [ID] [hook+instruction] Never use .unwrap() in production
     → Blocks: \.unwrap\(\)

## Project (this project only)
  4. [ID] [instruction] Use the repository pattern for data access

Detected stack: rust
Total: 4 rules (2 hook-enforced, 2 instruction-only)

For each rule show:

  • The rule ID (for use with /forget)
  • Enforcement type in brackets
  • Rule text
  • If hook-enforced: the pattern that triggers blocking (with →)

Also show the detected stack and totals.

If there are no rules, tell the user: "No rules set. Use /remember <rule> to add one."

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.

  1. yesterday First seen · 53 lines · 38 tokens per session scan A 717a909f99da

Subscribe to this mod's changes

rules is a skill published in the GitHub repository Lexxes-Projects/obey (1 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 388 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-31.

Related

Other skills, from other repositories

wordpress-plugin-fundamentals

Modern WordPress plugin development with PHP 8.3+, OOP architecture, hooks system, database interactions, and Settings API.

bobmatnyc/claude-mpm-skills · 32 tokens

dsh-hooks-authoring

编写或调试已安装的 dsh-hooks-plugin 的 hook 脚本。配置在 /.dsh/hooks.json,事件挂 PreToolUse/PostToolUse/UserPromptSubmit/SessionStart 等;命令从 toolinput.command 读,决策只能通过 stdout JSON 表达(permissionDecision deny/ask/allow),退出码不 gate,hookEventName 必须回填,Windows 上 command 由 PowerShell 解释且可能被沙箱拦外部 exe。.

KYinCode/dsh-hooks-plugin · 112 tokens

claude-automation-recommender

Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what…

mahmoud20138/Tradecraft · 77 tokens

Guard Rules

This skill should be used when a command is blocked by claude-guard, when the response contains "BLOCKED by claude-guard", when the user asks "why was my command blocked", "what commands are blocked", "guard rules", "safety rules", or when Claude is about to execute a potentially dangerous command. Covers git force…

hex/claude-guard · 190 tokens

taiyi-ui-design

TaiyiForge 第 4 阶段 — UI/UX 契约,产出 UI-DESIGN.md。四端通用。.

Dong90/oh-my-taiyiforge · 35 tokens

taiyi-evolve

TaiyiForge 辅助 — 实现后架构与文档同步(architecture-sync)。OpenCode / Claude / Codex / Cursor 通用。.

Dong90/oh-my-taiyiforge · 37 tokens