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.
npx agentmods add instructions/loonghao/rez-next/agents-mdgit clone --depth 1 https://github.com/loonghao/rez-nextWrote 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/loonghao/rez-next/agents-md)<a href="https://agentmods.dev/instructions/loonghao/rez-next/agents-md"><img src="https://agentmods.dev/badge/instructions/loonghao/rez-next/agents-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.01935 | $0.01935 |
| Opus 5 | $0.00967 | $0.00967 |
| Sonnet 5 | $0.00387 | $0.00387 |
| Haiku 4.5 | $0.00194 | $0.00194 |
Grade A, and why
rez-next 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 3d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rez-next - AI Agent Guide
Progressive disclosure map — start here, then follow links to details.
Disclosure chain: this file → llms.txt (concise AI index) → llms-full.txt (full API reference) → docs/ (human guides)
Project Overview
rez-next is a high-performance Rust rewrite of the Rez package manager with Python bindings. It supports common Rez workflows without mirroring Rez's internal implementation modules.
Key facts for agents:
- Language: Rust 2024 edition (MSRV 1.95) + Python 3.9+ bindings (PyO3 abi3)
- Build system: Cargo workspace (20 crates) + Maturin for Python
- Current version: 0.3.6 (see CHANGELOG.md)
- License: Apache 2.0
- Python API: curated top-level interfaces backed by native PyO3 modules
- CLI: 28 subcommands (config, context, view, env, release, test, build, search, bind, depends, solve, cp, mv, rm, status, diff, pkg-help, plugins, pkg-cache, suites, bundle, pip, complete, forward, gui, parse-version, self-test, self-update)
- Status: Common workflows work with
import rez_next as rez; internal namespaces such asrez.utilsare intentionally not mirrored.
Quick Start
# Drop-in replacement for most use cases
import rez_next as rez
from rez_next.packages_ import iter_packages, get_latest_package
from rez_next.resolved_context import ResolvedContext
# Supported top-level API
ctx = rez.resolve_packages(["python-3.9", "maya-2024"])
pkg = rez.get_latest_package("python")
Documentation Map
For AI Agents (this file is the primary entry point)
- CLAUDE.md → Anthropic Claude-specific guidance (references this file)
- GEMINI.md → Google Gemini-specific guidance (references this file)
- llms.txt → AI-friendly concise usage index (Python submodules, crate map, quick commands)
- llms-full.txt → Complete API reference (Rust + Python + CLI + benchmarks)
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.
- 3d ago First seen · 204 lines · 1,935 tokens per session scan A bcd3b1c92630
rez-next AGENTS.md is an instructions file published in the GitHub repository loonghao/rez-next (25 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,935 tokens to every session, about $0.0097 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-09-02.
Other instructions, from other repositories
monty CLAUDE.md
Claude Code instructions for pydantic/monty, covering claude.md, project overview, monty-types — shared boundary types, cross-platform requirements and important security notice.
NexusTrader CLAUDE.md
Instructions for Quantweb3-com/NexusTrader, covering claude.md, project overview, development commands, dependencies and setup and install with uv (package manager used in this project).
epistemic-graph AGENTS.md
Instructions for Knuckles-Team/epistemic-graph, covering agents.md — epistemic graph compute engine, epistemic os surfaces in the main build, commands for ai agents, python api (out-of-process client — not in-process) and async.
depyler CLAUDE.md
Instructions for paiml/depyler, covering claude.md - depyler compiler implementation protocol, critical: contract-first design, prime directive, project context and python packaging protocol.
depyler GEMINI.md
Instructions for paiml/depyler, covering depyler: python to rust transpiler, critical: contract-first design, project overview, key features and getting started.
rayt GEMINI.md
Gemini CLI instructions for gkmngrgn/rayt, covering project overview, building and running, basic rendering (cpu), high-quality rendering (cpu) and gpu rendering.