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/zackiles/deno-kit/with-deno-kit-contextgit 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-deno-kit-context)<a href="https://agentmods.dev/rules/zackiles/deno-kit/with-deno-kit-context"><img src="https://agentmods.dev/badge/rules/zackiles/deno-kit/with-deno-kit-context.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.00479 |
| Opus 5 | $0.00000 | $0.00239 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
with-deno-kit-context 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 3d 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
Context on this Project
- This codebase represents a CLI-based project scaffolder for Deno 2 projects (not Deno 1)
- The CLI supports several types of projects such as an http-server, CLI, library etc...
- Files in the folder
<project-root>/src/represent the CLI code - Files in the folder
<project-root>/templates/represent template files that are used to scaffold a users project and contain placeholders that the CLI replaces with values when compiling them in the users workspace for their new project - There is a top-level sub-folder in
<project-root>/templates/for each type of project the CLI can scaffold. E.g there is a folder named<project-root>/templates/clithat contains templates for a CLI project. - Templates that are shared across scaffold projects can be found in the
<project-root>/templates/sharedfolder. If there is a conflict between a shared template and project-specifc template, the project specific template takes precedence. For example,<project-root>/templates/cli/README.mdand<project-root>/templates/shared/README.mdboth exist, and so the project-specific one of<project-root>/templates/cli/README.mdtakes precesdence - The command file that compiles templates and scaffolds a user's project is in
src/commands/init.ts. In production it will download the github release templates.zip folder which contains all the templates intemplates/as they are shown now in the codebase, unzips them, compiles them with the runtime values a user provides, and then assembles a project with them (using some of the shared templates, with some of the project-specific ones) - IMPORTANT: because of the nature of the templates in
templates/local development of the templates is difficult and error prone. This is because of templates having either a) placeholders and b) paths that don't represent the final compiled path on a users machine. We don't get proper intellisense and linting or typechecking the files will not work. - Template files deno.jsonc config file when developing locally obviously also don't work as they can't properly resolve local files such as the entry point as they don't exist when developing localling. These files only work once compiled.
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.
- 3d ago First seen · 16 lines · 0 tokens per session scan A 8b542627200c
with-deno-kit-context is a cursor rule published in the GitHub repository zackiles/deno-kit (3 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 479 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
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
ts
Cursor rule "ts" from un-pany/v3-admin-vite, covering ts 开发规范, 类型, 命名, 代码组织 and 错误处理.
svelte
You are an expert in Svelte 5, SvelteKit, TypeScript, and modern web development.
bundling
The project uses a custom type bundling system to provide full TypeScript IntelliSense support in the Monaco editor for @bubblelab/bubble-core and its dependencies. This is necessary because Monaco cannot directly resolve workspace packages or external dependencies.
typescript-patterns
TypeScript patterns for code organization, classes, types, and symbols as it relates to this project.
ts-inspect
Use ts-inspect for exact TypeScript semantic type information (parameters, return types, properties, signatures, definitions, type at a location) instead of reading many source files or guessing from call sites.