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/kws-projects/react-boilerplate/maintaining-boilerplategit clone --depth 1 https://github.com/kws-projects/react-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.00008 | $0.00702 |
| Opus 5 | $0.00004 | $0.00351 |
| Sonnet 5 | $0.00002 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
maintaining-boilerplate 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining This Boilerplate
This repo is a starter template. When extending it, keep it generic, documented, and easy to fork.
Common tasks
- Add a UI component:
npx shadcn@latest add <component>(lands insrc/components/shadcn/), then create asrc/components/ui/<component>.tsxwrapper that re-exports or extends it. App code imports fromui/only. See theadd-shadcn-componentskill. - Adapt this starter into a new project: see the
customize-starterskill. - Add a feature: create
src/features/<feature>/withcomponents/,hooks/,api/,types/as needed. Keep features self-contained. - Add a language: create
src/i18n/locales/<lang>/common.json, register it insrc/i18n/config.ts(resources,supportedLanguages), and add tortlLanguagesif it is right-to-left. - Add a translation key: update every locale file under
src/i18n/locales/. - Add an env var: update
src/config/env.ts,.env.example, andsrc/vite-env.d.tstogether. - Wire a real integration: implement the SDK behind the existing adapter in
src/lib/analytics.tsorsrc/lib/monitoring.ts; do not scatter SDK calls. See theanalytics-and-monitoringskill for patterns. - Add a color: add CSS variables in
:rootand.darkinsrc/index.css, register in@theme inline, then use as Tailwind classes. See thecolor-managementskill. Never use raw hex/rgb/oklch in component classNames.
Analytics & Monitoring
- Analytics (
src/lib/analytics.ts): typed GA4 adapter using gtag.js. Feature code callsanalytics.track(...)or uses theuseAnalytics()hook. New event types go insrc/types/analytics.ts. Never callwindow.gtagdirectly outside ofanalytics.ts. - Monitoring (
src/lib/monitoring.ts): Sentry adapter. Feature code callsmonitoring.captureException(...)or uses theuseMonitoring()hook. The app is wrapped inSentryErrorBoundaryinApp.tsx. React 19 error hooks are wired inmain.tsx. Never import@sentry/reactdirectly outside ofmonitoring.ts. - Hooks (
src/hooks/):useAnalytics,useMonitoring, andusePageTracking— prefer these in components for testability. - Types (
src/types/):analytics.ts(event definitions),monitoring.ts(error context, user, breadcrumbs),global.d.ts(window augmentation for dataLayer).
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 · 56 lines · 8 tokens per session scan A b65fde7c803c
maintaining-boilerplate is a cursor rule published in the GitHub repository kws-projects/react-boilerplate (3 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 702 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
app_rules
This document outlines the essential rules and guidelines for developing with the MobileLauncher LT boilerplate. Follow these rules to maintain consistency, scalability, and code quality across the project.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
server-actions
Guidelines for Server Actions — validation, error handling, and when to use Route Handlers instead.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.
database-design
Database schema design patterns for Supabase with proper types and relationships.
hydration-safety
React hydration mismatch prevention.