coding_practices-documentation-jsdoc

coding_practices-documentation-jsdoc is a cursor rule for Cursor from PerkyZZ999/MemorizedMCP. It costs 128 tokens per session, scanned A, original, MIT.

A set of JavaScript documentation rules focused on JSDoc comments, which are structured notes describing code for people and documentation tools.

In plain words
What is it for?
Use it when setting coding guidelines or reviewing JavaScript documentation. It also calls for generating documentation during the build so published docs stay current.
Why use it?
It gives a project consistent expectations for documenting functions, classes, methods, parameters, return values, errors, examples, and complex data types.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when setting coding guidelines or reviewing JavaScript documentation. It also calls for generating documentation during the build so published docs stay current.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/perkyzz999/memorizedmcp/coding_practices-documentation-jsdoc
Install

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.

Clone the repo
git clone --depth 1 https://github.com/PerkyZZ999/MemorizedMCP

Made for: Cursor.

Wrote 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.

agentmods badge for coding_practices-documentation-jsdoc

README.md
[![agentmods](https://agentmods.dev/badge/rules/perkyzz999/memorizedmcp/coding_practices-documentation-jsdoc/github.svg)](https://agentmods.dev/rules/perkyzz999/memorizedmcp/coding_practices-documentation-jsdoc)
Your own site
<a href="https://agentmods.dev/rules/perkyzz999/memorizedmcp/coding_practices-documentation-jsdoc"><img src="https://agentmods.dev/badge/rules/perkyzz999/memorizedmcp/coding_practices-documentation-jsdoc/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.

agentmods 80×15 button for coding_practices-documentation-jsdoc

Your own site · 80×15
<a href="https://agentmods.dev/rules/perkyzz999/memorizedmcp/coding_practices-documentation-jsdoc"><img src="https://agentmods.dev/badge/rules/perkyzz999/memorizedmcp/coding_practices-documentation-jsdoc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 128 This file is loaded in full into every session.
When invoked 128 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00128 $0.00128
Opus 5.5 $0.00051 $0.00051
Sonnet 5.5 $0.00026 $0.00026
Haiku 4.5 $0.00013 $0.00013

Measured 1mo ago against content hash d435068de7d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coding_practices-documentation-jsdoc 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.

.cursor/rules/coding_practices-documentation-jsdoc.mdc · 20 lines

What it actually says

CODING_PRACTICES

Guidelines for DOCUMENTATION

JSDOC
  • Document all functions, classes, and methods with consistent JSDoc comments
  • Use @param, @returns, and @throws tags to document function behavior comprehensively
  • Implement @example tags with realistic usage scenarios for {{complex_apis}}
  • Use @typedef for documenting complex object structures when not using TypeScript
  • Configure documentation generation as part of the build process to keep docs current
  • Implement custom templates to match {{project_style_guidelines}}
Changes

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.

  1. 1mo ago First seen · 20 lines · 128 tokens per session scan A d435068de7d8

Subscribe to this mod's changes

coding_practices-documentation-jsdoc is a cursor rule published in the GitHub repository PerkyZZ999/MemorizedMCP (7 stars, last pushed 11mo ago), licensed MIT. It adds 128 tokens to every session, about $0.0005 per session on Opus 5.5. 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.