Borrowing it
Nothing to install: this file belongs to chaxus/ran. 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/chaxus/ran/main/AGENTS.mdgit clone --depth 1 https://github.com/chaxus/ranWrote 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/chaxus/ran/agents-md)<a href="https://agentmods.dev/instructions/chaxus/ran/agents-md"><img src="https://agentmods.dev/badge/instructions/chaxus/ran/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/chaxus/ran/agents-md"><img src="https://agentmods.dev/badge/instructions/chaxus/ran/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.00695 | $0.00695 |
| Opus 5.5 | $0.00278 | $0.00278 |
| Sonnet 5.5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
ran 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 today.
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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in ran
Start with the owner of the change; do not load every reference or introduce a second standard.
| Work | Read first |
|---|---|
| Visual hierarchy, composition, tokens and craft | ranui design standard |
| Input, focus, drafts, feedback and recovery | interaction standard |
| Optional batch/queue, settings, account/data or revision workflow | workflow patterns, only when relevant |
| Unsure which reference owns a decision | Short interface index |
| Component state, events, lifecycle or SSR | engineering standard, then implementation reference |
| Exact attributes, events, slots, parts or theme variables | Generated component API and public tokens; verify against source |
| Public documentation or localized prose | documentation site reference |
| Repository landing/demo identity | root DESIGN.md, scoped to that surface |
packages/ranui/theme/tokens.less and packages/ranui/theme/dark.less own foundation tokens. Product semantic aliases may derive from them;
do not create a parallel palette or copy one application's dimensions into library defaults.
The index routes decisions; workflow recipes describe host responsibilities, not extra ranui APIs.
For visual changes, use the UI task lookup to find exact owner sections and an evidence brief. Read only applicable owner sections; reuse existing controls and local token mappings. Stop when the contract, smallest patch and evidence are clear. Optional recipes do not require new infrastructure.
Run affected-package checks appropriate to the change and report evidence, not assumptions. The local scope below does not weaken the complete repository CI gates:
- Documentation:
pnpm verify:links,pnpm verify:docs, and changed-file Prettier checks. - Localized documentation:
pnpm -F docs check:langschecks labels, mirrored page structure and copy coverage. - Design:
pnpm -F ranui verify:designfor ranui changes (or the affected package's existing gate); root CI runspnpm verify:designacross its configured packages. Static gates do not prove layout or keyboard behaviour. - Guide/token/package examples:
pnpm -F ranui exec vitest run test/unit/docs.interface-guidance.test.ts. - Library behaviour: follow CODING's verification checklist, including relevant unit, integration, SSR and real-browser checks. Regenerate API/token docs from source.
Public ranui guidance has English and Chinese entry points under packages/docs/src/ranui/
and packages/docs/cn/src/ranui/. Link to canonical owners instead of duplicating long rules.
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.
- today Changed · +2 lines · +38 tokens per session 52c43aa3f1bf
- 3d ago First seen · 36 lines · 657 tokens per session scan A f5e4024c548e
ran AGENTS.md is an instructions file published in the GitHub repository chaxus/ran (269 stars, last pushed today), licensed MIT. It adds 695 tokens to every session, about $0.0028 per session on Opus 5.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-10-19.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.