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/project-coregit 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/project-core)<a href="https://agentmods.dev/rules/s0vers/next-app-i18n-starter/project-core"><img src="https://agentmods.dev/badge/rules/s0vers/next-app-i18n-starter/project-core.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.00293 | $0.00293 |
| Opus 5 | $0.00147 | $0.00147 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
project-core 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 5d 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
Project core
Tooling
- Use bun (or pnpm). Do not add npm/yarn lockfiles.
- Node 24.x. Run
bun run buildafter meaningful Next.js/i18n changes. - Run
bun run lintwhen editing TypeScript or ESLint config.
Environment
- Never modify
.envor commit env files. Document new vars in.env.exampleonly. - Canonical URL:
NEXT_PUBLIC_SITE_URL→ consumed bysrc/lib/site.ts.
Code changes
- Smallest correct diff; no unrelated refactors or new abstractions for one-liners.
- Match existing import style (
@/…aliases), naming, and file layout. - shadcn primitives live in
src/components/ui/— extend viacomponents.json, don't fork casually. - Prefer CSS transitions over animation libraries unless motion is explicitly requested.
Git
- Commit only when the user asks. No "Made-with: Cursor" in commit messages.
- Do not commit
.next/,node_modules/, or.env*.
Docs
- Long-form guides:
README.mdandpublic/llms.txt. - Agent rules:
.cursor/rules/— keep rules short; update rules when conventions change.
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.
- 5d ago First seen · 35 lines · 293 tokens per session scan A cedf314e976e
project-core is a cursor rule published in the GitHub repository s0vers/next-app-i18n-starter (64 stars, last pushed 2mo ago), licensed MIT. It adds 293 tokens to every session, about $0.0015 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-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.
commit
Conventional Commits specification and git commit workflow rules.
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
browser-debug-setup
One-time setup for a persistent debug browser on 127.0.0.1:9222 for dev-browser --connect. Use when browser work is needed but no reusable debug browser is running yet.
agent-browser-issue
Open a concise GitHub follow-up for reusable browser-use limitations. Use when browser automation is blocked by a likely tool-side issue that is worth fixing separately, especially for clicks, dropdowns, file inputs, focus traps, or other repeatable agent/browser failures.