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/aidenybai/react-grab/agents-mdgit clone --depth 1 https://github.com/aidenybai/react-grabWhat 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 | $0.02639 | $0.02639 |
| Opus 5 | $0.01319 | $0.01319 |
| Sonnet 5 | $0.00528 | $0.00528 |
| Haiku 4.5 | $0.00264 | $0.00264 |
Grade A, and why
react-grab 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 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.
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Rules
- MUST: Use @antfu/ni. Use
nito install,nr SCRIPT_NAMEto run.nunto uninstall. - MUST: Use TypeScript interfaces over types.
- MUST: Keep all types in the global scope.
- MUST: Use arrow functions over function declarations
- MUST: Default to NO comments. Only add a comment when the user explicitly asks, or when the "why" is truly non-obvious - browser quirks, platform bugs, performance tradeoffs, fragile internal patching, or counter-intuitive design decisions. Never add comments that restate what the code does or what a well-named function/variable already conveys. When in doubt, leave the comment out.
- Do not delete descriptive comments >3 lines without confirming with the user
- MUST: Use kebab-case for files
- MUST: Use descriptive names for variables (avoid shorthands, or 1-2 character names).
- Example: for .map(), you can use
innerXinstead ofx - Example: instead of
movedusedidPositionChange
- Example: for .map(), you can use
- MUST: Frequently re-evaluate and refactor variable names to be more accurate and descriptive.
- MUST: Do not type cast ("as") unless absolutely necessary
- MUST: Remove unused code and don't repeat yourself.
- MUST: Always search the codebase, think of many solutions, then implement the most elegant solution.
- MUST: Put all magic numbers in
constants.tsusingSCREAMING_SNAKE_CASEwith unit suffixes (_MS,_PX). - MUST: Put small, focused utility functions in
utils/with one utility per file. - MUST: Use Boolean over !!.
- MUST: No dynamic imports (
import()) unless strictly necessary (e.g. code-splitting a large optional dependency, breaking a circular dependency that cannot be refactored). Prefer staticimportat the top of the file.
V8 Hot-Path Rules
For hot per-frame paths (pointer/scroll handlers, animation ticks, fiber walks):
- MUST: Keep indirect call sites monomorphic. Do not pass different callbacks to a shared recursor/iterator that gets hot - split into one specialized helper per callback, or inline the loop.
- MUST: Mutate object fields in place instead of replacing the field with a fresh object literal.
obj.target.x = ...notobj.target = { x, y, ... }. Allocating per-frame literals churns the GC and cycles hidden classes. - MUST: Keep numeric helpers in a single number-type "lane". A function that early-returns a Smi (
return 8) and otherwise returns a double (labelWidth * 0.2) will deopt every consumer withnot a Smi. Pick one (e.g.Math.roundthe double). - SHOULD: Prefer closed-form arithmetic over loops that subtract/add a constant until a delta is in range (e.g. angle normalization with
Math.round(delta / 360), notwhile delta > 180).
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 First seen · 159 lines · 2,639 tokens per session scan A 6db107a45c4b
react-grab AGENTS.md is an instructions file published in the GitHub repository aidenybai/react-grab (7,595 stars, last pushed 10d ago), licensed MIT. It adds 2,639 tokens to every session, about $0.0132 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.
Other instructions, from other repositories
recharts AGENTS.md
Instructions for recharts/recharts: This is Recharts repository. Recharts is a React-based charting library. The goal is to provide a simple, declarative, and composable way to build charts. We value consistency, usability, and performance. Accessibility is important.
lingo.dev CLAUDE.md
Instructions for lingodotdev/lingo.dev, covering extremely important instructions for claude, fyi, tools, testing and changesets.
freemap-v3-react AGENTS.md
Instructions for FreemapSlovakia/freemap-v3-react, covering project notes for ai agents, reference docs, keeping llms.txt in sync, workflow and translations.
wp-react-kit AGENTS.md
Instructions for ManiruzzamanAkash/wp-react-kit, covering agents.md, project, commands, directory map and admin app (wp-admin).
wp-react-kit CLAUDE.md
Instructions for ManiruzzamanAkash/wp-react-kit, covering claude.md, project, commands, directory map and admin app.
KKTerm CLAUDE.md
Claude Code instructions for ryantsai/KKTerm: Constitution, Repository workflow, domain language, source-area boundaries, i18n rules, and engineering defaults live in AGENTS.md. Product terminology lives in CONTEXT.md. Read both before changing behavior or terminology.