rpg-encoder CLAUDE.md

Project instructions for a Rust workspace that builds Repository Planning Graphs, which represent relationships in source code to support code understanding through MCP. They define build, test, branch, and commit practices.

In plain words
What is it for?
Formatting and checking Rust code, running the workspace tests, building the release MCP binary, naming branches, and preparing linked pull requests.
Why use it?
They set the checks and issue-based workflow required before changes are merged, helping catch formatting, warning, and test failures.

Instructions file

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 instructions/userfrm/rpg-encoder/claude-md
Clone the repo
git clone --depth 1 https://github.com/userFRM/rpg-encoder
Per session 807 This file is loaded in full into every session.
When invoked 807 The same file — it is already loaded in full.
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.00807 $0.00807
Opus 5 $0.00404 $0.00404
Sonnet 5 $0.00161 $0.00161
Haiku 4.5 $0.00081 $0.00081

Measured 2d ago against content hash abff6fcff71b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

CLAUDE.md · 77 lines

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 fixes
  • feat/* — new features
  • docs/* — documentation only
  • chore/* — tooling, deps, version bumps

Commits

Use conventional commits:

  • fix: bug fix
  • feat: new feature
  • chore: tooling, version bump, deps
  • docs: documentation
  • refactor: code restructure (no behavior change)
  • test: adding or fixing tests

Issue-first workflow

  1. Open a GitHub issue describing the problem or feature
  2. Create a branch from main (fix/issue-description or feat/issue-description)
  3. Make commits on the branch
  4. Open a PR referencing the issue (Closes #N or Ref #N)
  5. Merge via squash merge (gh pr merge --squash --delete-branch)
  6. Pull main locally after merge

Release process

  1. Bump version in root Cargo.toml ([workspace.package] version) AND npm/package.json
  2. Run cargo fmt && cargo clippy --workspace --all-targets -- -D warnings && cargo test --workspace
  3. Commit: chore: bump version to X.Y.Z
  4. Tag: git tag vX.Y.Z
  5. Push: git push origin main && git push origin vX.Y.Z
  6. 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)

Read the full file on GitHub · 77 lines

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. 2d ago First seen · 77 lines · 807 tokens per session scan A abff6fcff71b

Subscribe to this mod's changes

rpg-encoder CLAUDE.md is an instructions file published in the GitHub repository userFRM/rpg-encoder (33 stars, last pushed 3mo ago), licensed MIT. It adds 807 tokens to every session, about $0.0040 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-30.