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/seogit 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/seo)<a href="https://agentmods.dev/rules/s0vers/next-app-i18n-starter/seo"><img src="https://agentmods.dev/badge/rules/s0vers/next-app-i18n-starter/seo.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.00368 |
| Opus 5 | $0.00000 | $0.00184 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
seo 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 6d 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
SEO
Single source of truth
src/lib/site.ts—siteConfig,openGraphLocales- Copy:
dictionary/{locale}/Metadata(title,description,keywords)
Canonical and hreflang URLs
Use getLocaleUrl / getAlternateLanguages from @/lib/site — never duplicate hreflang maps in layout and sitemap.
const canonical = await getLocaleUrl(locale, "/your-path");
const languages = await getAlternateLanguages("/your-path");
| Locale | Path |
|---|---|
en |
/ |
| others | /{locale} |
generateMetadata
- Set
metadataBase: new URL(siteConfig.url). alternates.canonical+alternates.languagesfor allrouting.locales.- OG image:
/og-image.png(1200×630 inpublic/).
Sitemap (src/app/sitemap.ts)
- One entry per logical page with
alternates.languages— not duplicate rows per locale. - New pages: add entry with
getPathname({ locale, href: "/your-path" })for each locale.
New page SEO checklist
- Meta keys in all dictionary files
- Page-level
generateMetadatawith canonical - Sitemap entry with hreflang alternates
- Optional JSON-LD in Server Component only
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.
- 6d ago First seen · 45 lines · 0 tokens per session scan A 7f9521cc85a7
seo 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 368 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.
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.
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
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.
hard-cut
Remove a feature completely with no backward compatibility. Use when the user says "hard cut", "rip it out", "delete it", "unship", "kill this feature", or wants dead code removed instead of deprecated. Delete the surface, callers, tests, docs, comments, fallbacks, and stubs.