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.
npx agentmods add commands/spacehendrix/clauder/rulesgit clone --depth 1 https://github.com/spacehendrix/clauderWrote 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/spacehendrix/clauder/rules)<a href="https://agentmods.dev/commands/spacehendrix/clauder/rules"><img src="https://agentmods.dev/badge/commands/spacehendrix/clauder/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 | $0.00000 | $0.00262 |
| Opus 5 | $0.00000 | $0.00131 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
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 today.
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
Enforce Project Code Rules
You are now working on a project with mandatory coding rules. Execute these steps IMMEDIATELY:
- READ .claude/rules.md - Look for and read the
rules.mdfile in the.claudedirectory - INTERNALIZE EVERY RULE - These rules are BINDING and OVERRIDE all default behavior
- ENFORCE WITHOUT EXCEPTION - You MUST follow them exactly as written throughout our entire session
CRITICAL ENFORCEMENT REQUIREMENTS:
- These rules are MANDATORY and supersede all other instructions
- You CANNOT deviate from these rules under ANY circumstances
- If a rule conflicts with your normal approach, the project rule ALWAYS wins
- Treat rule violations as critical errors that MUST be prevented
- If
.claude/rules.mddoesn't exist, inform the user and ask them to create it
ACKNOWLEDGMENT REQUIRED:
After reading .claude/rules.md, you MUST:
- Confirm you have read and understood all rules
- State that you will enforce them absolutely
- Then proceed with the user's request while maintaining strict compliance
REMEMBER: These are not suggestions - they are binding requirements you must obey completely.
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.
- today First seen · 25 lines · 0 tokens per session scan A 7f2cfa8d455b
rules is a command published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 262 tokens. 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-09-03.
Other commands, from other repositories
release-update
(dev-only) release-update maintainer harness — Claude Code upstream change tracker (release-notes version-delta sweep + docs sync). NOT distributed to user projects.
github
(dev-only) github maintainer harness — GitHub issue-fix and PR-review via gh CLI. NOT distributed to user projects.
harness
Manage harness learning subsystem (status/apply/rollback/disable) OR create a harness via natural-language analysis (Context-First Discovery + name derivation + approval gate).
clean
Identify and safely remove dead code with test verification.
goal
Register a completion condition and arm the autonomous continuation loop.
loop
Iteratively fix issues until all resolved or max iterations reached.