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 instructions/moonrunnerkc/ruleprobe/claude-mdgit clone --depth 1 https://github.com/moonrunnerkc/ruleprobeWhat 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.01062 | $0.01062 |
| Opus 5 | $0.00531 | $0.00531 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
ruleprobe CLAUDE.md 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 2d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Instructions for Claude (Claude Code, Claude SDK, claude.ai) when working on the RuleProbe codebase.
The full engineering rules live in AGENTS.md. Read that file first. Everything below is Claude-specific workflow guidance that supplements it. When the two conflict, AGENTS.md wins.
Project
- Repository: https://github.com/moonrunnerkc/ruleprobe
- Package: https://www.npmjs.com/package/ruleprobe
- Language: TypeScript (strict)
- Runtime: Node.js >= 18
Working Style
- Make targeted edits over full rewrites when a specific issue is flagged.
- Never pad documentation, README, or release notes with marginal results. Only genuinely interesting findings belong.
- Run verification before treating any feature as done:
npm testandnpm run build. - Push back when a claim is not backed by real data. Do not invent metrics, repo counts, or compliance scores.
- Use
git statusandgit diffto confirm what you actually changed before reporting completion.
Engineering Standards
These are enforced by the self-check workflow (RuleProbe verifies its own codebase). Following them keeps the build green.
- Always use TypeScript strict mode.
- Never use
any. Useunknownand narrow. - Always use named exports. Never use default exports.
- Use kebab-case for filenames.
- Use camelCase for variables and functions.
- Use PascalCase for types, interfaces, and classes.
- Prefer
constoverlet. - Prefer
interfaceovertypefor object shapes. - Files must stay under 300 lines.
- Add full JSDoc to every exported symbol.
- Never use em dashes anywhere.
- No magic numbers without a named constant.
Tooling
- Use
npmas the package manager. - Use
vitestas the test runner. - Use
eslintfor linting andprettierfor formatting. - Do not introduce competing tools (no biome, no jest, no pnpm).
Pipeline Boundaries
When editing pipeline code, respect the three-stage boundary: parse, verify, report. Each stage is independently testable and lives under its own directory in src/.
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.
- 2d ago First seen · 104 lines · 1,062 tokens per session scan A 8efc56fe25c7
ruleprobe CLAUDE.md is an instructions file published in the GitHub repository moonrunnerkc/ruleprobe (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,062 tokens to every session, about $0.0053 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.
Other instructions, from other repositories
deep-init copilot-instructions.md
Instructions for deepfusionlabs/deep-init, covering repository instructions (copilot projection), kemal — agent context, architecture, components (7) and critical to know (non-obvious, load-bearing).
vibe-27 AGENTS.md
AGENTS.md instructions for fatalex27/vibe-27, covering vibe-27 behavioral guidelines, 1. editor, not typist, 2. intention over implementation, 3. trust and verify and 4. think before coding.
vibe-27 CLAUDE.md
Claude Code instructions for fatalex27/vibe-27, covering vibe-27 behavioral guidelines, 1. editor, not typist, 2. intention over implementation, 3. trust and verify and 4. think before coding.
fable-method AGENTS.md
Instructions for Sahir619/fable-method, covering agents.md - the fable method, usage, step 0 - classify the ask, step 1 - define done and step 2 - gather evidence.
AGENTS.md AGENTS.md
Instructions for Anbeeld/AGENTS.md, covering global instructions, priorities, boundaries, uncertainty and evidence.
awesome-grok-build AGENTS.md
Instructions for DominikTobureto/awesome-grok-build, covering agents.md, mission, operating principles, source policy and file conventions.