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-typescriptgit clone --depth 1 https://github.com/zackiles/deno-kitWhat 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.02174 | $0.02174 |
| Opus 5 | $0.01087 | $0.01087 |
| Sonnet 5 | $0.00435 | $0.00435 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
with-typescript 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 2d 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
100% identical to with-typescript — 0 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: globs: *.ts alwaysApply: false
Rules For Typescript Types
Follow these rules and standards when creating or editing types:
- The less code it takes to define a type the better
- Derive dynamic types from values instead of repeating values that already exist
- Reuse and extend existing types instead of creating whole new types
- BAD: duplicating types in the project
- BAD: redundant type declaration
- BAD: manual type annotation
- BAD: non-inferential typing
- Consolidate or share similar types across files instead of creating similar ones for each file. Examples:
- Finding and using the
types.tsfile or common export if they exist - By namespace merging and augmentation of very similar interfaces that exist across files instead of creating the same or similar type in every single file.
- Finding and using the
- GOOD type-level programming or type inference-driven type construction
- GOOD: typeof inference: capturing runtime shapes for type use
- GOOD: mapped types: transforming types over keys
- GOOD: indexed access types: extracting types via
[K] - GOOD: template literal types: for strings and key construction.
- GOOD: conditional types: shaping types based on logic
Examples: GOOD Typescript Methods
The following Typescript methods are preferred.
-
satisfies-
Ensures a value conforms to a type without losing literal types
-
const config = { mode: 'dev', verbose: true, } satisfies Record<string, unknown>
-
-
-
infer-
Extracts types inside conditional types
-
type ElementType<T> = T extends (infer U)[] ? U : T
-
-
-
keyofwithtypeof-
Gets literal keys from objects or arrays
-
const flags = ['--help', '--verbose'] as const type Flag = (typeof flags)[number] // "--help" | "--verbose"
-
-
-
ReturnType,Parameters,ConstructorParameters-
Extracts return values, arguments, and constructor params from functions
-
type Fn = (x: number) => string type R = ReturnType<Fn> // string
-
-
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.
- 2d ago First seen · 352 lines · 2,174 tokens per session scan A a078079edf37
with-typescript is a cursor rule published in the GitHub repository zackiles/deno-kit (3 stars, last pushed 5mo ago), licensed MIT. It adds 2,174 tokens to every session, about $0.0109 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to with-typescript, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values. Enforced by the no-family-vocabulary Biome plugin plus lint:framework-vocabulary.
no-barrel-files
Avoid barrel files and unnecessary re-exports.
interface-factory-pattern
Interface-based design with factory functions (keep classes private).
explicit-opt-in-over-diagnostics
Prefer requiring explicit opt-in over emitting diagnostics on intentional user paths.