Borrowing it
Nothing to install: this file belongs to moonrunnerkc/ruleprobe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moonrunnerkc/ruleprobe/main/CLAUDE.mdgit clone --depth 1 https://github.com/moonrunnerkc/ruleprobeWrote 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/instructions/moonrunnerkc/ruleprobe/claude-md)<a href="https://agentmods.dev/instructions/moonrunnerkc/ruleprobe/claude-md"><img src="https://agentmods.dev/badge/instructions/moonrunnerkc/ruleprobe/claude-md/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/instructions/moonrunnerkc/ruleprobe/claude-md"><img src="https://agentmods.dev/badge/instructions/moonrunnerkc/ruleprobe/claude-md.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.01062 | $0.01062 |
| Opus 5.5 | $0.00425 | $0.00425 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (3 stars, last pushed 23d ago), licensed MIT. It adds 1,062 tokens to every session, about $0.0042 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.