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/zackiles/deno-kitWrote 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/zackiles/deno-kit/with-tests)<a href="https://agentmods.dev/rules/zackiles/deno-kit/with-tests"><img src="https://agentmods.dev/badge/rules/zackiles/deno-kit/with-tests/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/zackiles/deno-kit/with-tests"><img src="https://agentmods.dev/badge/rules/zackiles/deno-kit/with-tests.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.00316 |
| Opus 5.5 | $0.00000 | $0.00126 |
| Sonnet 5.5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
with-tests 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
Steps To Running or Reading Tests
-
Determine the commands, arguments, and path of the code file that runs the tests by searching for the nearest package file that typically will list the available test runners and commands. For example, this is often a
package.json,deno.jsonfile that exposes the projectsscripts, and hopefully a set of test commands. -
Review the entry point of the test runner to understand what global utilities, patterns, strategies, logging, and high-level capabilities are implemented so you're able debug any issues with the tests if you run into any while running them.
-
When errors occur always use all the information available to you, obvious or hidded, to contexualize any error messages you output to a user, or go retrieve more information to supplement with the error message or log.
CAUTION: HUMANS OFTEN DON'T FIND PLAIN LOG MESSAGES HELPFUL, AND THEY'LL PUNISH YOU IF YOU'RE NOT HELPFUL. ALWAYS SUPPLEMENT SUPPLEMENT PLAIN LOGS WITH OTHER CONTEXUAL DATA POINTS AND ANALYSIS UNLESS THE LOGS ARE ROBUST, AND FIND WAYS TO MAKE COMPLICATED LOGS SIMPLER. APPLY FORMATTING THAT MAKES LOGS EASY TO READ IN YOUR OUTPUT, SUCH AS PRETTY PRINTING, GROUPING, AND LABELING SO YOUR HUMAN WONT PUNISH YOU.
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 · 15 lines · 316 tokens per session scan A 6c18329a4753
with-tests is a cursor rule published in the GitHub repository zackiles/deno-kit (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 316 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
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.