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/spences10/sveltestWrote 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/spences10/sveltest/testing)<a href="https://agentmods.dev/rules/spences10/sveltest/testing"><img src="https://agentmods.dev/badge/rules/spences10/sveltest/testing/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/spences10/sveltest/testing"><img src="https://agentmods.dev/badge/rules/spences10/sveltest/testing.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.00102 | $0.00102 |
| Opus 5.5 | $0.00041 | $0.00041 |
| Sonnet 5.5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
testing 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 1mo 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
Svelte Testing
Read the shared testing skill and its relevant references before writing or changing tests. Keep reusable testing guidance there, not in this editor-specific entry point.
Follow AGENTS.md for repository conventions.
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.
- 1mo ago Changed · -243 lines · -1,716 tokens per session ecf307fcaa58
- 1mo ago First seen · 258 lines · 1,818 tokens per session scan A 70286da7980f
testing is a cursor rule published in the GitHub repository spences10/sveltest (113 stars, last pushed today), licensed MIT. It adds 102 tokens to every session, about $0.0004 per session on Opus 5.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
praman-cli
Praman CLI patterns for SAP UI5 test automation with playwright-cli.
praman
Praman v1.0 — SAP UI5 Test Automation Platform for Playwright.
tests
Praman test writing rules — Vitest unit tests and Playwright integration tests.
svelte
You are an expert in Svelte 5, SvelteKit, TypeScript, and modern web development.
cursor-rules-appendable
Praman SAP UI5 Test Automation Rules.
cursor-rules
Playwright E2E testing rules for {{PROJECTNAME}}; the full skill lives in .agents/skills/playwright-e2e.