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/backendforth/next-sanity-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/backendforth/next-sanity-starter/modules)<a href="https://agentmods.dev/rules/backendforth/next-sanity-starter/modules"><img src="https://agentmods.dev/badge/rules/backendforth/next-sanity-starter/modules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/backendforth/next-sanity-starter/modules"><img src="https://agentmods.dev/badge/rules/backendforth/next-sanity-starter/modules.svg" alt="Reviewed on agentmods" width="80" 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.00257 |
| Opus 5.5 | $0.00000 | $0.00103 |
| Sonnet 5.5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
modules 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
The wiring checklist (six points, inline opt-in) is in AGENTS.md §"The module pattern". Prefer pnpm gen:module <Name>; pnpm check:wiring compares every list.
- i18n: module fields are
internationalizedArray*; the projection returns the full arrays and the component resolves them withpickLocalizedString/pickLocalizedPortableTextBlocks. - File
module<Name>.ts,export const module<Name>andname: "module.<id>"must match —check:wiringfinds a module only by all three. - Give every module schema a
preview, or Studio lists each instance as "Untitled". - Renaming
module.<id>once content exists needs a data migration. - Module components are server components. An interactive part goes behind a lazy client boundary like
web/src/components/media/LazyVideo.tsxor…/carousel/LazyCarouselViewport.tsx, or it lands in every route's first-load JS.
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 Changed · -21 lines ed65c568d8fa
- 2d ago Changed 5f84c64febfa
- 1mo ago First seen · 37 lines · 0 tokens per session scan A 9cf5b06ff76b
modules is a cursor rule published in the GitHub repository backendforth/next-sanity-starter (4 stars, last pushed yesterday), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 257 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-31.
Other cursor rules, from other repositories
frontend
React/Next.js frontend coding standards with shadcn/ui, Tailwind CSS v4, and FSD-lite architecture.
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
agent-development
Python agents are typically in folders named agent-py/ or agent/ and use the sdk-python/ package.
test-running
When running tests, use the --watch false flag to avoid watch mode.
design-tokens-guide
The single source of truth for all design tokens is located in packages/design-tokens/src/tokens.ts.
lint-format-guide
Cursor rule "lint-format-guide" from first-fluke/fullstack-starter, covering lint & format guide, quick commands, check all, from root and python (in apps/api or apps/worker).