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/dtyq/magicWrote 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/dtyq/magic/testing-guide)<a href="https://agentmods.dev/rules/dtyq/magic/testing-guide"><img src="https://agentmods.dev/badge/rules/dtyq/magic/testing-guide/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/dtyq/magic/testing-guide"><img src="https://agentmods.dev/badge/rules/dtyq/magic/testing-guide.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.05005 | $0.05005 |
| Opus 5.5 | $0.02002 | $0.02002 |
| Sonnet 5.5 | $0.01001 | $0.01001 |
| Haiku 4.5 | $0.00500 | $0.00500 |
Grade A, and why
testing-guide scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
fetch(url, { signal: controller.signal }) The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 First seen · 761 lines · 5,005 tokens per session scan A cb9ac3c38fbb
testing-guide is a cursor rule published in the GitHub repository dtyq/magic (5,051 stars, last pushed 2mo ago), with no licence file. It adds 5,005 tokens to every session, about $0.0200 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
test-document-knowledge-base
When testing or our pdf.js annotations.
running-frontend-tests
How to run frontend component tests.
langsmith_evaluation
Comprehensive guide for LangSmith evaluation with @google/genai, including setup, dataset creation, target functions, evaluators, and running evaluations.
unit-test-manners
When implementing unit tests, adhere to the following principles to ensure robust, maintainable, and fast tests.
case-design
A test-case design workflow that turns requirements or prototypes into test cases in Markdown or Excel, with coverage analysis.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.