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/robotostudio/turbo-start-sanity/frontend-rulesgit clone --depth 1 https://github.com/robotostudio/turbo-start-sanityWrote 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/robotostudio/turbo-start-sanity/frontend-rules)<a href="https://agentmods.dev/rules/robotostudio/turbo-start-sanity/frontend-rules"><img src="https://agentmods.dev/badge/rules/robotostudio/turbo-start-sanity/frontend-rules.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.00227 |
| Opus 5 | $0.00000 | $0.00113 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
frontend-rules 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
Component Structure
- Prefer
gridoverflexunless working with two sibling tags - Use
flexfor simple parent-child layouts:
<div>
<img />
<p>Some text</p>
</div>
- Always use appropriate semantic HTML
- Use
SanityImagefor any images generated in Sanity if the component is available - Use
Buttons.tsxresolver for any buttons unless specified otherwise
Internationalization Rules
Only apply these rules when specifically asked about internationalization:
| Replace | With |
|---|---|
| left | start |
| right | end |
| ml | ms |
| mr | me |
| pl | ps |
| pr | pe |
| border-l | border-s |
| border-r | border-e |
| text-left | text-start |
| text-right | text-end |
| float-left | float-start |
| float-right | float-end |
For buttons with directional arrows, use an RTL prop to correctly handle horizontal inversion.
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 · 41 lines · 0 tokens per session scan A 02d5572667b2
frontend-rules is a cursor rule published in the GitHub repository robotostudio/turbo-start-sanity (176 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 227 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
nextjs-pages
App Router pages, layouts, and route handlers under [locale].
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
rtl-right-to-left-i18n-cursorrules-prompt-file
Cursor rules for RTL development with logical CSS properties, Tailwind logical classes, bidirectional text, and automated auditing via rtlify-ai.
i18n-mandatory
All user-visible UI text uses t('namespace:section.key') from react-i18next.
i18n-boundary
有 UI 的 consumer 定義或變更 i18n 涵蓋範圍、硬編碼語言 surface、翻譯 lint 與 server error localization 邊界時適用.
nuxt-error-localization
UI 錯誤訊息必須本地化（繁體中文），禁止直接顯示原始英文 error code 或 message.