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/snoozbuster/is-smm-beaten-yet/scripts-and-datagit 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/scripts-and-data)<a href="https://agentmods.dev/rules/snoozbuster/is-smm-beaten-yet/scripts-and-data"><img src="https://agentmods.dev/badge/rules/snoozbuster/is-smm-beaten-yet/scripts-and-data.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.00000 | $0.00208 |
| Opus 5 | $0.00000 | $0.00104 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
scripts-and-data 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
Scripts and data pipeline
Scripts in scripts/ are part of the data pipeline: they consume the OneDrive dataset (and optionally the Google sheet) and produce static files the webapp expects.
Do not change script output paths or JSON shapes without checking consumers:
- constants/levelData.ts —
DATA_ROOT_URL, expected paths - Composables and components that fetch
uncleared.json,clear_summary.json,course-data/{levelId}/, etc.
Environment: Mix of Node (ESM) and Python. See script usage (e.g. -o=, -i=, -d=) in each file.
Do: Keep output formats and paths in sync with what the app fetches.
Don't: Rename or restructure outputs without updating the app and docs.
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 · 21 lines · 0 tokens per session scan A 0deeffd18acc
scripts-and-data is a cursor rule published in the GitHub repository snoozbuster/is-smm-beaten-yet (43 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 208 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
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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.