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/s0vers/next-app-i18n-starter/componentsgit clone --depth 1 https://github.com/s0vers/next-app-i18n-starterWrote 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/s0vers/next-app-i18n-starter/components)<a href="https://agentmods.dev/rules/s0vers/next-app-i18n-starter/components"><img src="https://agentmods.dev/badge/rules/s0vers/next-app-i18n-starter/components.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.00000 | $0.00319 |
| Opus 5 | $0.00000 | $0.00160 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
components 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 4d 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
Components
Organization
src/components/pages/— page-level compositions (e.g.HomeIndex.tsx)src/components/ui/— shadcn primitives (Button, Card, Tabs, …)- Feature components at
src/components/root
Client vs server
- Add
"use client"only when using hooks, events, or browser APIs. - Prefer Server Components for pages; pass translated strings or use
NextIntlClientProvider(set in layout).
Styling
- Tailwind CSS 4 +
cn()from@/lib/utils. - Use CSS variables from
globals.cssfor theme tokens.
RTL
- Arabic sets
dir="rtl"on<html>. - Keep code, numbers, logos LTR with
OmitRTLfrom@/components/OmmitRlt:
<OmitRTL omitRTL>
<pre><code>{command}</code></pre>
</OmitRTL>
Theme
- No
next-themes. Theme: cookie SSR (src/lib/theme.ts) +ThemeProvider+ModeToggle. - Do not inject blocking scripts for theme flash prevention.
UI additions
- New shadcn components: follow
components.jsonaliases (@/components,@/lib/utils). - Icons:
lucide-react.
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.
- 4d ago First seen · 45 lines · 0 tokens per session scan A d52607dd8834
components is a cursor rule published in the GitHub repository s0vers/next-app-i18n-starter (64 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 319 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-30.
Other cursor rules, from other repositories
components
React component architecture for creating composable, accessible components with data attributes. Use when creating/updating composable components, not for higher-level feature/page components.
react
React patterns with destructured props, compiler optimization, Effects, and Tailwind v4 syntax. ALWAYS use when using React.
ai-collaboration
Instructions for AI agent code generation workflow.
api-validation
API route validation — enforces Zod validation on all route handlers and server actions.
error-handling
Error boundaries, loading states, and server error handling.
file-uploads
Image and file upload patterns — prevents insecure client-side uploads and missing file validation.