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/stefaniuk/loadout/reactjsgit clone --depth 1 https://github.com/stefaniuk/loadoutWhat 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.03448 | $0.03448 |
| Opus 5 | $0.01724 | $0.01724 |
| Sonnet 5 | $0.00690 | $0.00690 |
| Haiku 4.5 | $0.00345 | $0.00345 |
Grade A, and why
loadout reactjs.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 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ReactJS Engineering Instructions ⚛️
These instructions define React-specific patterns for building high-quality applications with modern hooks and component architecture.
They must remain applicable to:
- React 19+ functional components with hooks
- Single Page Applications (SPA) and Server-Side Rendering (SSR)
- Component libraries and design systems
- Mobile-responsive web applications
For general language and tooling guidance, defer to:
- typescript.instructions.md - strict typing, quality gates, testing tiers
This file covers only what that file does not: React component design, hooks patterns, state management, and UI-specific concerns.
They are non-negotiable unless an exception is explicitly documented (with rationale and expiry) in an ADR/decision record.
Identifier scheme. Every normative rule carries a unique tag in the form [RJS-<prefix>-NNN], where the prefix maps to the containing section (for example QR for Quick Reference, CMP for Component Design, HK for Hooks, STM for State Management). Use these identifiers when referencing, planning, or validating requirements.
0. Quick reference (apply first) 🧠
This section exists so humans and AI assistants can reliably apply the most important rules even when context is tight.
- [RJS-QR-001] Functional components only: no class components; use hooks for all stateful logic ([RJS-CMP-001]).
- [RJS-QR-002] Component size limit: split components exceeding ~150 lines or 3 responsibilities ([RJS-CMP-003]).
- [RJS-QR-003] Hooks at top level: never call hooks inside loops, conditions, or nested functions ([RJS-HK-001]).
- [RJS-QR-004] Exhaustive deps: include all referenced values in dependency arrays; use ESLint rule ([RJS-HK-002]).
- [RJS-QR-005] Cleanup effects: return cleanup functions from effects that subscribe, listen, or allocate ([RJS-HK-004]).
- [RJS-QR-006] Props as interface: define props as a TypeScript
interface(nottypealias); avoidReact.FC([RJS-CMP-005]). - [RJS-QR-007] Error boundaries: wrap feature boundaries with Error Boundaries; provide fallback UI ([RJS-ERR-001]).
- [RJS-QR-008] Semantic HTML first: use native elements before ARIA;
<button>not<div onClick>([RJS-A11Y-001]). - [RJS-QR-009] No inline object/array props: define outside render or memoize to prevent child re-renders ([RJS-PERF-001]).
- [RJS-QR-010] Controlled forms: use controlled inputs with explicit value/onChange; avoid uncontrolled refs for form state ([RJS-FRM-001]).
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 · 222 lines · 3,448 tokens per session scan A 0cd87df1e672
loadout reactjs.instructions.md is an instructions file published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 3d ago), licensed MIT. It adds 3,448 tokens to every session, about $0.0172 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-31.
Other instructions, from other repositories
apm cli.instructions.md
CLI Design Guidelines for visual output, styling, and user experience standards.
apm integrators.instructions.md
Architecture rules for file-level integrators (BaseIntegrator pattern).
apm cicd.instructions.md
CI/CD Pipeline configuration for PyInstaller binary packaging and release workflow.
apm encoding.instructions.md
Cross-platform encoding rules — keep all source and CLI output within printable ASCII.
spec-driven-steroids AGENTS.md
Instructions for lindoelio/spec-driven-steroids, covering agents.md, project identity, technology stack, essential commands and agent constraints.
featherspec constitution.instructions.md
FeatherSpec constitution editing rules (thin loader).