comment-usage

comment-usage is a cursor rule for Cursor from claire-gong-18/awesome-cursorrules. It costs 102 tokens per session, scanned A, a copy of comment-usage, CC0-1.0.

A code rule for writing comments that explain why unusual code exists, rather than repeating what obvious code already does.

In plain words
What is it for?
Use it when adding, reviewing, or maintaining comments in a codebase.
Why use it?
Too many vague or outdated comments make code harder to read. Focused comments preserve useful context without adding clutter.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when adding, reviewing, or maintaining comments in a codebase.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/claire-gong-18/awesome-cursorrules/comment-usage
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/claire-gong-18/awesome-cursorrules

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 comment-usage

README.md
[![agentmods](https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/comment-usage.svg)](https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/comment-usage)
Your own site
<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/comment-usage"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/comment-usage.svg" alt="Measured on agentmods" height="20"></a>
Per session 102 This file is loaded in full into every session.
When invoked 102 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 100% copy Near-identical to another mod 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.00102 $0.00102
Opus 5 $0.00051 $0.00051
Sonnet 5 $0.00020 $0.00020
Haiku 4.5 $0.00010 $0.00010

Measured 3d ago against content hash 547a43d7092e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

comment-usage 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 3d 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.

Origin

This is a copy

100% identical to comment-usage — 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.

rules/github-cursorrules-prompt-file-instructions/comment-usage.mdc · 8 lines

What it actually says

  • Use comments sparingly, and when you do, make them meaningful.
  • Don't comment on obvious things. Excessive or unclear comments can clutter the codebase and become outdated.
  • Use comments to convey the "why" behind specific actions or explain unusual behavior and potential pitfalls.
  • Provide meaningful information about the function's behavior and explain unusual behavior and potential pitfalls.
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. 3d ago First seen · 8 lines · 102 tokens per session scan A 547a43d7092e

Subscribe to this mod's changes

comment-usage is a cursor rule published in the GitHub repository claire-gong-18/awesome-cursorrules (0 stars, last pushed 1y ago), licensed CC0-1.0. It adds 102 tokens to every session, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to comment-usage, differing in 0 lines, and is treated as a copy.