Borrowing it
Nothing to install: this file belongs to rimio-ai/rimz. 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/rimio-ai/rimz/main/AGENTS.mdgit clone --depth 1 https://github.com/rimio-ai/rimzWrote 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/rimio-ai/rimz/agents-md)<a href="https://agentmods.dev/instructions/rimio-ai/rimz/agents-md"><img src="https://agentmods.dev/badge/instructions/rimio-ai/rimz/agents-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/rimio-ai/rimz/agents-md"><img src="https://agentmods.dev/badge/instructions/rimio-ai/rimz/agents-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.04182 | $0.04182 |
| Opus 5 | $0.02091 | $0.02091 |
| Sonnet 5 | $0.00836 | $0.00836 |
| Haiku 4.5 | $0.00418 | $0.00418 |
Grade A, and why
rimz AGENTS.md scanned grade A with 1 finding 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 yesterday.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
**Top-level modules** — durable file mechanics: `disk` atomic publish and fsync, XDG paths, rotating JSONL append, workspace lock, single-flight election, stat-keyed parse cache, disk-usage measurement (`usage`); identit How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Invariant. RimZ routes attention: it surfaces which agent needs you and takes you straight to its pane, where you answer in the agent's own UI.
How to read this contract
Two kinds of statement live here, and they earn different deference.
Invariants are load-bearing: a product promise, an architectural boundary a cargo xtask invariants grep enforces, or a durability rule. Breaking one breaks the build or the product. The sections below say which statements are invariants. Change one deliberately, in its own commit, with the doc and the gate moving together.
Everything else is a default — the choice that has been right most of the time here. Follow it absent better information; depart when the work in front of you argues otherwise, and say why in the PR or hand-off. A default that keeps losing is a bug in this file, so fix the file.
Exercise judgment without asking on how to decompose a change, which tests earn their cost, and when a rule's rationale does not reach the case at hand. Push back when a request looks wrong, rests on a false premise, or has a simpler shape — an early correction beats a faithful implementation of the wrong thing. Ask when a wrong guess is expensive and a question is cheap.
Match the size of the change to the size of the ask, and leave the refactor you noticed on the way as a note unless it blocks you. When this map and the territory disagree, the code is what ships: follow the code, then fix the map in the same change.
Engineering principles
The house style is explicit Rust — typed IDs across module boundaries, structured parsers over ad-hoc string work, state machines where a bool would drift, typed Result errors at library boundaries — and rust-conventions.md is its authority. unwrap/expect/panic belong in tests, build scripts, and provably-impossible states — leave a comment naming why the state is impossible.
For an event or timing bug, write the red end-to-end test first and prove the proposed signal reaches the consumer's decision point: producer emission and timestamp freshness are not evidence of consumer freshness.
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.
- yesterday Changed · +24 tokens per session 3f1a0186aed9
- 2d ago Changed · +4 lines · +125 tokens per session c771f8ee98a7
- 3d ago Changed · +1 lines · +199 tokens per session b551230b6bbd
- 4d ago Changed · +1 lines · +17 tokens per session ab9af2a902fd
- 9d ago First seen · 138 lines · 3,817 tokens per session scan A 75dcbdeb0740
rimz AGENTS.md is an instructions file published in the GitHub repository rimio-ai/rimz (24 stars, last pushed yesterday), licensed MIT. It adds 4,182 tokens to every session, about $0.0209 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
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).
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).
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.
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.