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-project-folder)<a href="https://agentmods.dev/rules/zackiles/deno-kit/with-project-folder"><img src="https://agentmods.dev/badge/rules/zackiles/deno-kit/with-project-folder/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-project-folder"><img src="https://agentmods.dev/badge/rules/zackiles/deno-kit/with-project-folder.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.01650 |
| Opus 5.5 | $0.00000 | $0.00660 |
| Sonnet 5.5 | $0.00000 | $0.00330 |
| Haiku 4.5 | $0.00000 | $0.00165 |
Grade A, and why
with-project-folder 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.
This is a copy
88% identical to with-project-directory — 135 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critical Rules To Be Followed When Analyzing Or Editing Code In These Directories
The following directories are unique project directories that require you to follow all rules described for any files contained anywhere in a folder or sub-folder that matches these glob patterns: src/utils/**, bin/**, scripts/**
NOTE (Glob Pattern Relative Path): ALL glob patterns are relative to the root of the project or codebase. This is sometimes referred to as the worksapce root.
NOTE: Ignore default README.md files mentioned here if there is a README.md in directory AND that README.md talks specifically about the directory.
Rules:
- Before editing, creating, or analyzing files in one of the mentioned folders, read the folders strict rules defined in the directory-specific README.md contained in the root of the folder. For example, the following README.md files exist:
src/utils/README.md,bin/README.md,scripts/README.md. - Ensure ALL code you generate and any files created or modified in the directory or any of its sub-directories follow each rule defined in the README.md for that directory.
- All rules in the README.md defined as
MUSTshould always be followed. - All rules in the README.md defined as
MAYorSHOULDare recommended but can be ignored if it is reasonable to do so. - Things a user explicitly asks you to do that violates any of the rules mentioned can be followed, but ensure you remind them after your work is complete of the parts of your solution that didn't adhere to the rules and your rationale of why you didn't adhere to them.
Default README.md Files
When no README.md can be found in the folder that matches the glob patterns of: src/utils/**, bin/**, or scripts/** then you may use the following as the default rules. Use only the right rules for the right folder below.
scripts/README.md Default Rules
Purpose: The scripts/ directory is used to store general purpose, self-contained, executable scripts written in Typescript or Javascript.
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 · 109 lines · 0 tokens per session scan A c0c98bdba5a3
with-project-folder 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 1,650 tokens. A static security scan graded it A with 0 findings. It is 88% identical to with-project-directory, differing in 135 lines, and is treated as a copy.
Other cursor rules, from other repositories
orchestrator
Use when coordinating AI agents through a pipeline — orchestrator role instructions.
workspace
Multi-agent workspace context — loaded on every session.
engineering-agent-prompt-engineer
Use when writing, reviewing, or improving prompts for AI agents — agent role design and prompt engineering.
deno-lint
Deno lint error guidance.
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.