Borrowing it
Nothing to install: this file belongs to jnPiyush/AgentX. 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/jnPiyush/AgentX/master/.github/instructions/react.instructions.mdgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/react)<a href="https://agentmods.dev/instructions/jnpiyush/agentx/react"><img src="https://agentmods.dev/badge/instructions/jnpiyush/agentx/react/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/jnpiyush/agentx/react"><img src="https://agentmods.dev/badge/instructions/jnpiyush/agentx/react.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.00440 | $0.00440 |
| Opus 5.5 | $0.00176 | $0.00176 |
| Sonnet 5.5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
AgentX react.instructions.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 1mo 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.
What it actually says
React / TypeScript Instructions
Auto-loads when editing React files. For comprehensive standards, load the skill.
Skill: .github/skills/languages/react/SKILL.md
Key Rules
- Functional components only, with TypeScript interfaces for props
- Destructure props in function signature
- Custom hooks: extract reusable logic, prefix with
use - useCallback for callbacks passed to children
- useMemo for expensive computations
- React.memo for pure components
- React Query / TanStack Query for server state
- Zustand or Jotai for client state (avoid prop drilling)
- React Testing Library -- test behavior, not implementation
- MSW for API mocking in tests
- Always include alt text, use semantic HTML, ensure keyboard navigation
Critical Rules (Embedded -- Always Active)
Testing
- 80%+ code coverage required
- React Testing Library: query by role/label, NEVER by test-id unless no alternative
- Test user behavior (clicks, types, submits) not implementation details
- Use
screen.getByRole(),userEvent.click(),waitFor()for async - MSW for API mocking -- intercept at network level, not in component
Accessibility
- All images MUST have descriptive
alttext - All interactive elements MUST be keyboard-accessible
- Use semantic HTML (
<button>,<nav>,<main>,<article>) - Color contrast MUST meet WCAG 2.1 AA (4.5:1 for text)
- Test with
axe-coreorjest-axein automated tests
Security
- Sanitize any user-generated HTML (use
DOMPurify) - Never use
dangerouslySetInnerHTMLwithout sanitization - Validate all form inputs with
zodschemas at the boundary - Never store secrets or tokens in client-side code
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.
- 1mo ago Changed 652b229e694c
- 1mo ago First seen · 48 lines · 440 tokens per session scan A 015f345b539d
AgentX react.instructions.md is an instructions file published in the GitHub repository jnPiyush/AgentX (17 stars, last pushed 2d ago), licensed Apache-2.0. It adds 440 tokens to every session, about $0.0018 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-08-30.
Other instructions, from other repositories
create-trimble-app typescript.instructions.md
Instructions for julianoczkowski/create-trimble-app, covering typescript patterns for modus components, event type casting, common event types, component ref types and modal ref pattern.
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).