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-javascript)<a href="https://agentmods.dev/rules/zackiles/deno-kit/with-javascript"><img src="https://agentmods.dev/badge/rules/zackiles/deno-kit/with-javascript/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-javascript"><img src="https://agentmods.dev/badge/rules/zackiles/deno-kit/with-javascript.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.05681 |
| Opus 5.5 | $0.00000 | $0.02272 |
| Sonnet 5.5 | $0.00000 | $0.01136 |
| Haiku 4.5 | $0.00000 | $0.00568 |
Grade A, and why
with-javascript 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
86% identical to with-javascript — 252 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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CODING STYLE GUIDE - JAVASCRIPT AND TYPESCRIPT (MANDATORY OR STRONGLY ENCOURAGED)
Naming
- kebab-case: for file and folder names.
- camelCase: for instance names.
- PascalCase: for class and symbol names.
- UPPER_SNAKE_CASE: for constants.
- Consistent: When naming things, always review the naming patterns and conventions of similar this and follow that those
- Evolve Names Over Time: When refactoring previous code, look for opporutnities to rename not only the things you're working on but related things where renaming both would provide an overall better pattern, convention, or abstraction for the broader code base.
- Files and Folders:
- Single simple words until there are conflicts. Examples:
config.ts,commands/,logger.ts,data/',auth.ts` etc... - Folder names should be conventional, idiomatic, and shared-domain-neutral. Examples:
src/utils,scripts/,docs/,types.ts,src/coreetc... - Avoid deeply nesting folders, keep flat structures as long as possible.
- Single simple words until there are conflicts. Examples:
Naming Specificity
- Broad and abstract names for: namespaces, classes, types shared by multiple files, global concepts, project terms.
- Narrow or specific or descriptive names for local or specific things, or when other rules, instructions, or consistency in the codebase requires it.
Renaming and Refactoring Names
- IMPORTANT: Avoid renaming the following unless explicitly asked to: environment or global cinfug variable names, project or package names, import paths, file names, module names.
- After renaming things, find any JSDoc or inline comments that refer to the things that were named and update them to use the new names.
- After renaming things, ensure similar things that are named in a way that is similar to the previous name are also refactored to remain consistent naming patterns, conventions, and abstracions.
- Avoid renaming things in a way that would directly violate any instruction or rule provided to you, or indirectly cause side-effects in the final code that would violate other rules or instructions provided to 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 · 445 lines · 5,681 tokens per session scan A ecd25a9dafe8
with-javascript 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 5,681 tokens. A static security scan graded it A with 0 findings. It is 86% identical to with-javascript, differing in 252 lines, and is treated as a copy.
Other cursor rules, from other repositories
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
typescript-security
// NEVER: Hardcoded secrets const apiKey = "sk-proj-xxxxx".
ts
A set of TypeScript coding rules covering types, naming, file organization, error handling, and strict type checking. TypeScript is JavaScript with checks that help catch many mistakes before the program runs.
general-rule
Cursor rule "general-rule" from vinhnx/vtchat, covering development guidelines, tech stack & project overview, package management, code style and ui/ux design principles.
platform-pattern-2-filesystem-operations
Cursor rule "platform-pattern-2-filesystem-operations" from PaulJPhilp/EffectPatterns, covering platform pattern 2: filesystem operations and example.