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/Luxvil/ai-coding-rulesWrote 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/luxvil/ai-coding-rules/frontend)<a href="https://agentmods.dev/rules/luxvil/ai-coding-rules/frontend"><img src="https://agentmods.dev/badge/rules/luxvil/ai-coding-rules/frontend.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.00131 | $0.00131 |
| Opus 5 | $0.00066 | $0.00066 |
| Sonnet 5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
frontend 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.
What it actually says
Windsurf Rules - Frontend
Apply when working with React/Vue/Svelte components.
Component Structure
- One component per file
- Use named exports
- Colocate styles, tests, and types
React Patterns
- Prefer functional components with hooks
- Use React.memo() for expensive renders
- Prefer composition over inheritance
TypeScript
- Explicit return types on exports
- Use
interfacefor objects,typefor unions - Avoid
any— useunknownif unclear
Performance
- Lazy load routes and heavy components
- Optimize images
- Avoid unnecessary re-renders
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 · 28 lines · 131 tokens per session scan A 55a76b9b683b
frontend is a cursor rule published in the GitHub repository Luxvil/ai-coding-rules (3 stars, last pushed today), licensed MIT. It adds 131 tokens to every session, about $0.0007 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-09-08.
Other cursor rules, from other repositories
code-patterns
Rules for component structure, import patterns using @/ path aliases (never relative paths), import ordering, and TypeScript conventions.
rules.general
A project rule set for a Next.js application using TypeScript, React, Tailwind CSS, shadcn/ui, Radix UI, and Lucide icons.
virtual-environment
Rules for using Python virtual environments - check requirements.txt for installed libraries and use the existing virtual environment directory.
styling
Rules for styling - use Tailwind CSS only, no inline styles, use CSS variables for colors, monochromic design pattern, and button icon spacing guidelines.
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).