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/marcoturi/react-redux-boilerplate/agents-mdgit clone --depth 1 https://github.com/marcoturi/react-redux-boilerplateWhat 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.01682 | $0.01682 |
| Opus 5 | $0.00841 | $0.00841 |
| Sonnet 5 | $0.00336 | $0.00336 |
| Haiku 4.5 | $0.00168 | $0.00168 |
Grade A, and why
react-redux-boilerplate 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project overview
Production-ready React 19 boilerplate using vertical slice architecture. The stack is React 19 + Redux Toolkit 2 + Vite 7 + TypeScript 5.9 + Tailwind CSS 4 + Biome.
Setup commands
- Node version: 24.x (defined in
.nvmrc). Usefnm useornvm usebefore running commands. - Package manager: pnpm 10.x (
corepack enableif needed). - Install deps:
pnpm install - Create env:
pnpm create:env - Dev server:
pnpm dev(starts athttp://localhost:5173) - Build:
pnpm build(runstsc -b && vite build)
Testing
- Unit/integration tests:
pnpm test(Vitest 4 + Testing Library + jsdom) - With coverage:
pnpm test:coverage - E2E tests:
pnpm e2e:local(requires dev server running in another terminal) - E2E uses: Cucumber + Playwright. Install browsers first:
pnpm exec playwright install - Test files live next to the code they test with
.spec.ts/.spec.tsxsuffix. - Mock data files use
.mocks.spec.tssuffix and are excluded from test runs. - MSW (Mock Service Worker) handles API mocking in both tests and development.
- Vitest globals (
describe,it,expect,vi) are available without imports. - Always run
pnpm testandpnpm buildbefore submitting changes.
Linting, formatting, and type checking
- Single tool: Biome handles both linting and formatting. No ESLint or Prettier.
- Check all:
pnpm check(runsbiome check && tsc --noEmit) - Auto-fix:
pnpm check:fix(runsbiome check --write && tsc --noEmit) - Format only:
pnpm format - Lint only:
pnpm lint - Type check only:
pnpm type:check - Pre-commit hook (Husky) runs
pnpm biome check --stagedandpnpm testautomatically.
Code style
- TypeScript strict mode with
noImplicitAny: false. - Single quotes, semicolons, trailing commas, 2-space indent, LF line endings, 80 char line width.
- Use
import typefor type-only imports (enforced by BiomeuseImportType). - Prefer
for...ofover.forEach()(enforced by BiomenoForEach). - Use
constoverletwhen possible. Never usevar. - Use
unknowninstead ofanyfor error catches and untyped values. - Use
import.meta.envinstead ofprocess.envin browser/Vite code. - Use
null(notundefined) as the return value for components that render nothing. - Absolute imports via
@/alias (maps tosrc/). Never use relative imports that go above the current feature.
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.
- 3d ago First seen · 131 lines · 1,682 tokens per session scan A 198335034a0e
react-redux-boilerplate AGENTS.md is an instructions file published in the GitHub repository marcoturi/react-redux-boilerplate (103 stars, last pushed 5d ago), licensed MIT. It adds 1,682 tokens to every session, about $0.0084 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
magicui AGENTS.md
Instructions for magicuidesign/magicui, covering project context, key principles, before writing code, rules and accessibility (a11y).
playwriter AGENTS.md
Instructions for remorses/playwriter, covering backward compatibility, architecture, development, running mcp locally and running cli locally.
weapp-tailwindcss CLAUDE.md
Claude Code instructions for sonofmagic/weapp-tailwindcss, covering claude.md, project overview, monorepo structure, common development commands and build.
ui-components AGENTS.md
Instructions for starc007/ui-components, covering beui v2 — agent guide, commands, layout, component catalog and components (motion category — primitives).
OneJS AGENTS.md
Instructions for Singtaa/OneJS, covering onejs v3: agent guide, requirements, install, project setup and build and live reload.
Ataru AGENTS.md
Instructions for lovstudio/Ataru, covering agents.md, design system, quick rules, color palette and common patterns.