agentmods.dev

re_gent AGENTS.md

re_gent AGENTS.md is an instructions file for Codex, OpenCode from regent-vcs/re_gent. It costs 3,551 tokens per session, scanned A, original, Apache-2.0.

Project instructions for re_gent, a version-control system for recording what an AI coding agent changed, why it changed it, and how each step relates to earlier steps.

In plain words
What is it for?
They help contributors understand and implement re_gent's blame, log, and show concepts for tracing prompts, changes, and tool activity across sessions.
Why use it?
They provide the project's shared vocabulary and design decisions so agents can work consistently with its history and purpose.

Instructions file for CodexOpenCode

not rated 791 +4 2mo ago A scan 3,551 tokens original Apache-2.0
View the source file regent-vcs/re_gent re-gent.dev
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/regent-vcs/re_gent/agents-md
Clone the repo
git clone --depth 1 https://github.com/regent-vcs/re_gent

Made for: Codex, OpenCode.

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

agentmods badge for re_gent AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/regent-vcs/re_gent/agents-md.svg)](https://agentmods.dev/instructions/regent-vcs/re_gent/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/regent-vcs/re_gent/agents-md"><img src="https://agentmods.dev/badge/instructions/regent-vcs/re_gent/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,551 This file is loaded in full into every session.
When invoked 3,551 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.1 $0.03551 $0.03551
Opus 5 $0.01775 $0.01775
Sonnet 5 $0.00710 $0.00710
Haiku 4.5 $0.00355 $0.00355

Measured 5d ago against content hash 2a4cd41c9a66, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

re_gent AGENTS.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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 218 lines

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 Codex (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:

  • /compact and 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:

  1. Blob — raw bytes (file content, message body, JSON payload). Identified by blake3(content). Identical content stores once (free dedupe).
  2. Tree — { path → blob_hash, blame_hash } map describing the workspace at one moment. Itself a blob.
  3. 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.
  4. Ref — the only mutable object. A named pointer (e.g. refs/sessions/<session_id>) holding a step hash.

Read the full file on GitHub · 218 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. 5d ago First seen · 218 lines · 3,551 tokens per session scan A 2a4cd41c9a66

Subscribe to this mod's changes

re_gent AGENTS.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,551 tokens to every session, about $0.0178 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.

Git and workflowai-agentclaude-codedeveloper-toolsdevtoolsversion-control
Related

Other instructions, from other repositories

dev3000 AGENTS.md

Instructions for vercel-labs/dev3000, covering agents.md, runtime, local ui, production workflows, browser tools and development rules.

vercel-labs/dev3000 · 1,320 tokens

zvm CLAUDE.md

Claude Code instructions for tristanisham/zvm, covering claude.md, project overview, build & test commands, architecture and packaging & generated files.

tristanisham/zvm · 1,202 tokens

Grace AGENTS.md

AGENTS.md instructions for ScottArbeit/Grace, covering agent instructions, agent quickstart (local), issue tracking, development process and markdown guidelines.

ScottArbeit/Grace · 4,000 tokens

agent-inspect AGENTS.md

AGENTS.md instructions for rajudandigam/agent-inspect, covering agentinspect ai maintainer instructions, product boundary, source of truth, public-copy rule and start every task.

rajudandigam/agent-inspect · 1,932 tokens

jenkins-cli CLAUDE.md

Claude Code instructions for avivsinai/jenkins-cli, covering claude.md, build & test commands, run a single test, skip e2e tests during unit testing and e2e with colima on macos (if docker is unreachable).

avivsinai/jenkins-cli · 1,057 tokens

patchloom AGENTS.md

AGENTS.md instructions for patchloom/patchloom, covering agents.md, project overview, dev commands, git hygiene and release prs (release-please).

patchloom/patchloom · 9,594 tokens