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-jsdocgit 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.00007 | $0.03514 |
| Opus 5 | $0.00003 | $0.01757 |
| Sonnet 5 | $0.00001 | $0.00703 |
| Haiku 4.5 | $0.00001 | $0.00351 |
Grade A, and why
with-jsdoc scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
return await fetch(url, options); This is a copy
100% identical to with-jsdoc — 10 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 — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive JSDoc Comment Style Guide for AI Agents
This rule provides comprehensive guidance for writing JSDoc comments in modern TypeScript/JavaScript projects, ensuring they work correctly with advanced linting tools, type checkers, and documentation generators.
Ensuring JSDoc Compatibility: Critical Linting Considerations
Identifying and Respecting Project Linter Configurations
Before writing JSDoc comments, ALWAYS check for and respect the project's linting configuration in:
deno.jsonordeno.jsoncpackage.jsonorpackage.jsonc(eslint configuration).eslintrc.js,.eslintrc.json, or.eslintrc.yamlbiome.json.vscode/settings.json- Any other project-specific linting configuration files
Utilizing Inline Linting Control Comments for False Positives
Use inline linting controls when necessary to prevent false positives:
// For file-level ignores:
// @ts-nocheck
// deno-lint-ignore-file
// biome-ignore-file
// eslint-disable
// For line-level ignores:
// @ts-ignore
// deno-lint-ignore <rule-name>
// biome-ignore <rule-name>
// eslint-disable-next-line <rule-name>
Requirements for Validating JSDoc Code Examples
Code examples in JSDoc comments MUST:
- Be valid, compilable code that matches the codebase's style
- Include all necessary imports
- Use proper types that exist in the codebase
- Follow the project's linting rules
- Be properly escaped to prevent breaking documentation parsers
Core JSDoc Guidelines and Sections
Section 1: JSDoc Syntax Rules and Formatting Standards
Handling Special Characters: Escaping Double Asterisks
When documenting patterns containing double asterisks (**), use HTML entity * to escape each asterisk.
Example:
/**
* @example
* ```
* // BAD - Will break JSDoc parsers and linters
* glob('src/**/*.ts')
*
* // GOOD - Properly escaped
* glob('src/**/*.ts')
* ```
*/
Section 2: Essential JSDoc Decorators by Context
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.
- yesterday First seen · 398 lines · 7 tokens per session scan A e8ff39cf1bfa
with-jsdoc is a cursor rule published in the GitHub repository zackiles/deno-kit (3 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 3,514 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to with-jsdoc, differing in 10 lines, and is treated as a copy.
Other cursor rules, from other repositories
_code-rules-TypeScript
Apply when creating or editing TypeScript (.ts) files or shared TypeScript modules. Enforces typed, modular, readable code with strict formatting, naming, imports, configuration, validation, error handling, async patterns, and separation of concerns.
_code-rules-TypeScript-summary
Apply when creating or editing TypeScript (.ts) files or shared TypeScript modules. Enforces typed, modular, readable code with strict formatting, naming, imports, configuration, validation, error handling, async patterns, and separation of concerns. This is a concise summary of…
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
docs
This file provides guidelines for working with the documentation in the /docs directory.
architecture
Architecture of openapi-to-cli (ocli).
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.