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 rules/p-to-q/repo-template/frontend-reactgit clone --depth 1 https://github.com/p-to-q/repo-templateWrote 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/rules/p-to-q/repo-template/frontend-react)<a href="https://agentmods.dev/rules/p-to-q/repo-template/frontend-react"><img src="https://agentmods.dev/badge/rules/p-to-q/repo-template/frontend-react.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 | $0.00008 | $0.00135 |
| Opus 5 | $0.00004 | $0.00068 |
| Sonnet 5 | $0.00002 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
frontend-react 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.
What it actually says
Frontend React Stack Rule
For React/TypeScript frontend code:
- Prefer existing component and hook patterns already used in the codebase.
- Keep components focused and readable.
- Keep business logic out of presentational components where practical.
- Avoid deeply nested JSX when structure can be simplified.
- Prefer explicit props and readable state transitions.
- Reuse existing utilities and hooks before creating new ones.
- Do not introduce state abstractions or custom hooks unless they reduce real local complexity.
- Preserve existing UI behavior unless change is required.
- Keep type definitions readable and intention-revealing.
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 · 19 lines · 8 tokens per session scan A df07551a6b7a
frontend-react is a cursor rule published in the GitHub repository p-to-q/repo-template (2 stars, last pushed 27d ago), licensed Apache-2.0. It adds 8 tokens to every session and 135 once invoked, about $0.0000 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 cursor rules, from other repositories
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
frontend-web
Frontend web development guidelines for React, TanStack Router, and TanStack Query.
cursor-rules
How to add or edit Cursor rules in our project.
sync-shadcn
Autogoal-backed planning, status, review, dashboard, apply, and tracking for upstream shadcn docs syncs into Plate docs. Use when the user asks for sync-shadcn, sync-shadcn status, sync-shadcn review, sync-shadcn dashboard, sync-shadcn apply, a scoped sync-shadcn lane, to sync shadcn docs, audit newer shadcn docs…
plate-plan
Define or update Plate editor-behavior specs with a pass-gated, evidence-scored plan. Use for behavior law, authority maps, protocol rows, parity gates, research-backed winner shifts, editor chrome contracts, and implementation-roadmap changes.
clawsweeper
Triage and process the Slate v2 issue ledger with OpenClaw-style sweep discipline: archive-first discovery, duplicate proof, small-fix gates, exact claim rules, maintainer-safe issue output, and gitcrawl API refreshes.