Borrowing it
Nothing to install: this file belongs to regent-vcs/re_gent. 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/regent-vcs/re_gent/main/CLAUDE.mdgit clone --depth 1 https://github.com/regent-vcs/re_gentWrote 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/regent-vcs/re_gent/claude-md)<a href="https://agentmods.dev/instructions/regent-vcs/re_gent/claude-md"><img src="https://agentmods.dev/badge/instructions/regent-vcs/re_gent/claude-md.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.1 | $0.03549 | $0.03549 |
| Opus 5 | $0.01775 | $0.01775 |
| Sonnet 5 | $0.00710 | $0.00710 |
| Haiku 4.5 | $0.00355 | $0.00355 |
Grade A, and why
re_gent 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 8d 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.
This is a copy
92% identical to re_gent AGENTS.md — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
re_gent
Version control for AI agents. A content-addressed, DAG-based version control system that captures what an agent did, why (which prompt), and lets you blame, log, and inspect steps across sessions.
This document is the project's source of truth for context, vocabulary, and architectural decisions. It is the first file Claude (or any contributor) should read when working in this repo.
Mission
Today, AI coding agents have no version control of their own. Devs have built workarounds:
/compactand pray- copy-pasting code into a fresh chat
- screenshotting the "good" version before it changes
- "that was working five minutes ago"
- "go back to before the refactor"
- "why did you change that file"
- "i told you this already"
We gave agents write access to our codebases. We did not give ourselves git for it.
re_gent provides three primitives that should already exist for every agent-driven workflow:
- blame — which prompt produced this line of code?
- log — what did this session actually do, in causal order?
- show — inspect the full tool and conversation context for any step.
These three turn the agent's activity into something inspectable and shareable. They also unlock the next layer (branch, merge, rewind, multi-session orchestration) once the foundation is solid.
Tool & CLI
- Project name: re_gent
- CLI binary:
rgt(3 chars, ergonomic) - Storage directory:
.regent/at the project root (analogous to.git/) - License: Apache 2.0 — see
LICENSE
The conceptual model in 90 seconds
Four primitive object types, three immutable and content-addressed:
- Blob — raw bytes (file content, message body, JSON payload). Identified by
blake3(content). Identical content stores once (free dedupe). - Tree —
{ path → blob_hash, blame_hash }map describing the workspace at one moment. Itself a blob. - Step — analogous to a git commit.
{ parent, tree, transcript, causes, session_id, origin, turn_id, ... }. Itself a blob. Auto-generated by hooks, never hand-authored. - Ref — the only mutable object. A named pointer (e.g.
refs/sessions/<session_id>) holding a step hash.
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.
- 8d ago First seen · 218 lines · 3,549 tokens per session scan A 2e0db42bd871
re_gent CLAUDE.md is an instructions file published in the GitHub repository regent-vcs/re_gent (791 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 3,549 tokens to every session, about $0.0177 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to re_gent AGENTS.md, differing in 24 lines, and is treated as a copy.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.