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.
git clone --depth 1 https://github.com/ayimmam/PCICWrote 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/ayimmam/pcic/frontend-react)<a href="https://agentmods.dev/rules/ayimmam/pcic/frontend-react"><img src="https://agentmods.dev/badge/rules/ayimmam/pcic/frontend-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/rules/ayimmam/pcic/frontend-react"><img src="https://agentmods.dev/badge/rules/ayimmam/pcic/frontend-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.00000 | $0.00409 |
| Opus 5.5 | $0.00000 | $0.00164 |
| Sonnet 5.5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
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 2mo 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 Conventions
File Patterns
- Components:
client/src/components/{module}/ComponentName.jsx— PascalCase - Pages:
client/src/pages/PageName.jsx— PascalCase - Hooks:
client/src/hooks/useFeature.js— camelCase withuseprefix - UI primitives:
client/src/components/ui/— Shadcn generated, avoid editing directly
Component Rules
- JSX only — never use TypeScript (.tsx/.ts). No type annotations, no interfaces.
- Use
export default function ComponentName()for pages and feature components - Use
React.forwardReffor UI primitives (Shadcn pattern) - Use
@/path alias for all imports:import { Button } from "@/components/ui/button" - Styling is Tailwind CSS classes only — no CSS modules, no styled-components
- Use
cn()from@/lib/utilsto merge conditional classes
Data Fetching
- Always use React Query hooks from
client/src/hooks/:useEvents(),useDecisions(),useStrikes(),useCandidates(),useMembers()
- Mutations invalidate queries via
queryClient.invalidateQueries() - API errors are caught and shown via
toast.error()from Sonner
Forms
- Use
react-hook-form+zodschemas +@hookform/resolvers/zod - Define zod schema above the component, pass to
useForm({ resolver: zodResolver(schema) })
Auth / Access Control
- Wrap protected content in
<RoleGate allowedRoles={[...]}> - Never check roles inline — use the RoleGate component
- Auth state comes from
useAuth()hook (wraps AuthContext)
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.
- 2mo ago First seen · 42 lines · 0 tokens per session scan A d92e66d2ae5f
frontend-react is a cursor rule published in the GitHub repository ayimmam/PCIC (3 stars, last pushed 19d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 409 tokens. 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
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
react-components-creation-cursorrules-prompt-file
Cursor rules for React component creation and development.
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI integration.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.