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/bybren-llc/a-safe-pulse/11-frontend-reactgit clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote 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/bybren-llc/a-safe-pulse/11-frontend-react)<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/11-frontend-react"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/11-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.1 | $0.00000 | $0.00436 |
| Opus 5 | $0.00000 | $0.00218 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
11-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 today.
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.
This is a copy
100% identical to 11-frontend-react — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Frontend React Rules
These rules apply when working on frontend code in sdk/.
Technology Stack
- Framework: React 18
- Desktop: Electron
- UI Library: ShadCN UI components
- Styling: Tailwind CSS
- Type Safety: TypeScript (strict mode)
Component Patterns
- Use functional components with hooks (no class components)
- Use TypeScript interfaces for all props
- Follow ShadCN UI component patterns for consistency
- Use Tailwind utility classes for styling (avoid custom CSS)
Authenticated Pages
For pages requiring authentication, see patterns_library/ui/authenticated-page.md.
Forms
For forms with validation, see patterns_library/ui/form-with-validation.md (React Hook Form + Zod).
Data Tables
For paginated data tables, see patterns_library/ui/data-table.md.
State Management
- Use React hooks for local state
- Use context for shared state within feature boundaries
- Avoid prop drilling beyond 2 levels
API Integration
- All API calls must handle loading, error, and success states
- Use proper error boundaries so analytics/API failures do not crash the app
- Handle authentication token refresh transparently
Accessibility
- All interactive elements must be keyboard-navigable
- Use semantic HTML elements
- Include ARIA labels where needed
- Follow ShadCN UI's built-in accessibility patterns
Validation Commands
# TypeScript validation
{{TYPE_CHECK_COMMAND}}
# Linting
{{LINT_COMMAND}}
# Build verification
{{BUILD_COMMAND}}
Key References
- See
patterns_library/ui/for UI component patterns - See
docs/security/SECURITY_FIRST_ARCHITECTURE.mdfor client-side security - See
CONTRIBUTING.mdfor full workflow details
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.
- today First seen · 75 lines · 0 tokens per session scan A fcd6e6ba4712
11-frontend-react is a cursor rule published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 436 tokens. A static security scan graded it A with 0 findings. It is 100% identical to 11-frontend-react, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
ai-agent-specialist
Cursor rules for TypeScript, React, Node.js, clean architecture, testing, and WHY-oriented engineering guidance.
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
rust
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
05-web-development
Use the following format for code blocks.