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/snoozbuster/is-smm-beaten-yetWrote 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/snoozbuster/is-smm-beaten-yet/project-context)<a href="https://agentmods.dev/rules/snoozbuster/is-smm-beaten-yet/project-context"><img src="https://agentmods.dev/badge/rules/snoozbuster/is-smm-beaten-yet/project-context.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.00328 | $0.00328 |
| Opus 5 | $0.00164 | $0.00164 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
project-context 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 7d 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 context
This repo is the Is Super Mario Maker Beaten Yet? webapp: stats for Team 0%'s goal of clearing every Super Mario Maker 1 level before server shutdown.
Stack: Nuxt 3, Vue, TypeScript, PrimeVue, Tailwind CSS. Data is statically generated and served as JSON from a CDN; there is no traditional backend.
Project structure:
pages/— routescomponents/— UIcomposables/— shared logicconstants/,types/— level data and types (seeconstants/levelData.ts,types/levels.ts)scripts/— data pipeline (Node + Python); see.cursor/rules/scripts-and-data.mdcviewer/— forked SMM level parser/drawer (JS); see.cursor/rules/viewer-caution.mdcamplify/— Lambda functions; DiscordErrorNotifier is deployed; SyncLevelsGSheets is local-only and not deployed
Quality checks: Run yarn lint after editing; run yarn typecheck after editing .ts or .vue. ESLint covers .ts, .vue, and .js; typecheck covers only .ts/.vue (viewer/scripts .js are not type-checked). No unit tests; do not add test frameworks or tests unless specifically requested.
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.
- 7d ago First seen · 22 lines · 328 tokens per session scan A 127f69fc54a9
project-context is a cursor rule published in the GitHub repository snoozbuster/is-smm-beaten-yet (43 stars, last pushed 5mo ago), licensed MIT. It adds 328 tokens to every session, about $0.0016 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.