comments-javascript

A set of commenting rules for JavaScript and TypeScript files, including required file headers and function documentation.

In plain words
What is it for?
Use it to document files, functions, constants, modules, imports, outputs, examples, and expected error handling.
Why use it?
It keeps code explanations complete and current, including purpose, execution flow, dependencies, exports, parameters, results, and error cases.

Cursor rule

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.

agentmods
npx agentmods add rules/diegomarino/awesomic-cursor-rules/comments-javascript
Clone the repo
git clone --depth 1 https://github.com/diegomarino/awesomic-cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,670 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01670
Opus 5 $0.00000 $0.00835
Sonnet 5 $0.00000 $0.00334
Haiku 4.5 $0.00000 $0.00167

Measured yesterday against content hash 8691f034c53e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

rules/comments-javascript.mdc · 267 lines

How it starts

The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.

JavaScript Comments Standards

File Headers

Required format for all JavaScript/TypeScript files:

/**
 * @file [Brief file description]
 * @fileoverview [Detailed explanation of the file's purpose and functionality]
 *
 * [Additional context and important notes about the file]
 *
 * Functions:
 * - [List all functions included in this file with brief descriptions]
 * - Format: "functionName: brief description"
 * - Must be present even if empty
 *
 * Constants:
 * - [List all constants if the file defines them]
 * - Format: "CONSTANT_NAME: type - description"
 * - Must be present even if empty
 *
 * Flow:
 * 1. [Step one in execution flow]
 * 2. [Step two]
 * - Must describe the main flow of the file
 *
 * Error Handling:
 * - [Describe potential error cases and how they are managed]
 * - Format: "Error case: handling approach"
 * - Must describe all error scenarios
 *
 * @module [Module path or identifier]
 * @requires [Dependency name] - [Brief description]
 * @exports {Type} [Exported entity] - [Brief export description]
 */

Function Documentation

Required format for all functions and methods:

/**
 * [Short function description]
 *
 * [Detailed explanation of what the function does, including edge cases]
 *
 * @async (if applicable)
 * @function [functionName]
 * @param {Type} name - [Parameter description]
 * @returns {Type} [Return value description]
 * @throws {ErrorType} [Description of when this error occurs]
 * @example
 * // Example usage of the function
 * const result = myFunction(param);
 * // returns: expected output
 *
 * // Edge case example
 * const edgeResult = myFunction(edgeParam);
 * // returns: edge case output
 *
 */

Class Documentation

/**
 * [Class description]
 *
 * @class
 * @implements {Interface}
 * @augments ParentClass
 * @property {Type} propertyName - [Property description]
 * @example
 * const instance = new MyClass(config);
 * instance.method();
 * // returns: expected output
 *
 */

Read the full file on GitHub · 267 lines

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. yesterday First seen · 267 lines · 0 tokens per session scan A 8691f034c53e

Subscribe to this mod's changes

comments-javascript is a cursor rule published in the GitHub repository diegomarino/awesomic-cursor-rules (10 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,670 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.