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/horusgoul/eslint-plugin-react-render-types/agents-mdgit clone --depth 1 https://github.com/HorusGoul/eslint-plugin-react-render-typesWrote 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/horusgoul/eslint-plugin-react-render-types/agents-md)<a href="https://agentmods.dev/instructions/horusgoul/eslint-plugin-react-render-types/agents-md"><img src="https://agentmods.dev/badge/instructions/horusgoul/eslint-plugin-react-render-types/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.01239 | $0.01239 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
eslint-plugin-react-render-types 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project
ESLint plugin that brings Flow's Render Types to TypeScript via JSDoc @renders annotations. Enforces component composition constraints at lint time using typed linting.
Commands
pnpm build # Compile TypeScript (tsc → dist/)
pnpm test:run # Run all tests once (vitest)
pnpm test # Run tests in watch mode
pnpm typecheck # Type-check without emitting
pnpm lint # Lint src/ and tests/
Example project (example/)
pnpm install # Separate install (not a workspace)
pnpm lint # Run ESLint — errors expected in InvalidUsage.tsx
pnpm lint:update-snapshot # Regenerate lint-snapshot.txt after changing expected errors
pnpm typecheck # Type-check the example
Architecture
src/
index.ts # Plugin entry — exports rules + recommended config
rules/ # 5 ESLint rules
valid-render-return.ts Validates component returns match @renders declaration
valid-render-prop.ts Validates props/children with @renders receive correct components
valid-renders-jsdoc.ts Validates @renders JSDoc syntax (braces, PascalCase)
require-renders-annotation.ts Requires @renders on all components (off by default)
renders-uses-vars.ts Marks @renders references as used (prevents no-unused-vars)
utils/
cross-file-resolver.ts Resolves @renders and @transparent annotations across files via TypeScript's type checker
render-chain.ts Follows @renders chains (A → B → C) using type IDs
jsdoc-parser.ts Parses @renders/@transparent JSDoc annotations
jsx-extraction.ts Extracts component names from JSX (ternary, &&, .map())
component-utils.ts Component detection helpers
settings.ts Reads shared ESLint settings (additionalTransparentComponents)
types/
index.ts RendersAnnotation, ResolvedRendersAnnotation, ComponentTypeInfo
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 First seen · 118 lines · 1,239 tokens per session scan A fead00bf5b75
eslint-plugin-react-render-types AGENTS.md is an instructions file published in the GitHub repository HorusGoul/eslint-plugin-react-render-types (111 stars, last pushed 1mo ago), licensed MIT. It adds 1,239 tokens to every session, about $0.0062 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-04.
Other instructions, from other repositories
react-seed AGENTS.md
Instructions for guokaigdg/react-seed, covering agents.md, 目录, 1. 项目概览, 2. 技术栈 and 3. 目录结构.
primitives angular.instructions.md
Instructions for radix-ng/primitives, covering typescript best practices, angular best practices, components, state management and templates.
openbridge-webcomponents AGENTS.md
AGENTS.md instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering agents.md — universal ai agent instructions, 1. repository overview, source directory layout, 2. coding standards and comments.
vital CLAUDE.md
Instructions for jvidalv/vital, covering claude ai assistant guide, project overview, tech stack, core framework and styling.
Kokoro-Engine CLAUDE.md
Claude Code instructions for chyinan/Kokoro-Engine, covering claude.md, git 规范, 项目概述, 常用命令 and 安装依赖.
retry-axios GEMINI.md
Gemini CLI instructions for JustinBeckwith/retry-axios, covering project: retry-axios, project overview, building and running, dependencies and commands.