Borrowing it
Nothing to install: this file belongs to userFRM/rpg-encoder. 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/userFRM/rpg-encoder/main/CLAUDE.mdgit clone --depth 1 https://github.com/userFRM/rpg-encoderWrote 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/userfrm/rpg-encoder/claude-md)<a href="https://agentmods.dev/instructions/userfrm/rpg-encoder/claude-md"><img src="https://agentmods.dev/badge/instructions/userfrm/rpg-encoder/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/userfrm/rpg-encoder/claude-md"><img src="https://agentmods.dev/badge/instructions/userfrm/rpg-encoder/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.00807 | $0.00807 |
| Opus 5.5 | $0.00323 | $0.00323 |
| Sonnet 5.5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
rpg-encoder 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rpg-encoder
Rust workspace for building Repository Planning Graphs (RPGs) — semantic code understanding via MCP.
Build & Verify
cargo fmt --all # format
cargo clippy --workspace --all-targets -- -D warnings # lint
cargo test --workspace # test (640+ tests)
cargo build --release -p rpg-mcp # release binary
Before every commit: run fmt, clippy, and test. All three must pass. Do not skip or suppress warnings.
Git Workflow
Branch naming
fix/*— bug fixesfeat/*— new featuresdocs/*— documentation onlychore/*— tooling, deps, version bumps
Commits
Use conventional commits:
fix:bug fixfeat:new featurechore:tooling, version bump, depsdocs:documentationrefactor:code restructure (no behavior change)test:adding or fixing tests
Issue-first workflow
- Open a GitHub issue describing the problem or feature
- Create a branch from
main(fix/issue-descriptionorfeat/issue-description) - Make commits on the branch
- Open a PR referencing the issue (
Closes #NorRef #N) - Merge via squash merge (
gh pr merge --squash --delete-branch) - Pull main locally after merge
Release process
- Bump version in root
Cargo.toml([workspace.package] version) ANDnpm/package.json - Run
cargo fmt && cargo clippy --workspace --all-targets -- -D warnings && cargo test --workspace - Commit:
chore: bump version to X.Y.Z - Tag:
git tag vX.Y.Z - Push:
git push origin main && git push origin vX.Y.Z - The release workflow auto-builds binaries, creates a GitHub release, and publishes to npm
Project Structure
crates/
rpg-core/ # Graph data model, storage, schema, LCA
rpg-parser/ # Tree-sitter entity extraction (Rust, Python, JS/TS, Go, Java, C/C++)
rpg-encoder/ # Semantic lifting, grounding, dependency resolution
rpg-nav/ # Search, explore, fetch, export (navigation layer)
rpg-cli/ # CLI binary
rpg-mcp/ # MCP server binary (stdio JSON-RPC)
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 · 77 lines · 807 tokens per session scan A abff6fcff71b
rpg-encoder CLAUDE.md is an instructions file published in the GitHub repository userFRM/rpg-encoder (31 stars, last pushed 5mo ago), licensed MIT. It adds 807 tokens to every session, about $0.0032 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-30.
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.