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/braindao/adk-ts/no-commentsgit clone --depth 1 https://github.com/BrainDAO/adk-tsWhat 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.00278 | $0.00278 |
| Opus 5 | $0.00139 | $0.00139 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
no-comments 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- no-comments — 100% identical, 0 lines differ
What it actually says
Code Documentation Guidelines
Commenting Philosophy
This project follows a minimalist approach to code comments, focusing on clarity through well-structured, self-documenting code.
Comment Guidelines
-
Documentation Comments Only: Add comments only when they provide documentation value. The code itself should be clear enough to understand without excessive comments.
-
No Line-by-Line Comments: Avoid explaining each line of code with a comment. This creates maintenance overhead and often becomes outdated.
-
Method-Level Documentation: Place concise documentation comments above methods/functions to explain:
- Purpose of the method
- Complex logic that may not be immediately obvious
- Any important side effects
-
Class-Level Documentation: Document classes with a brief description of their purpose and responsibility.
-
Interface Documentation: Document interfaces with clear descriptions of their intent and contract.
When to Use Comments
✅ Good Use of Comments:
- Explaining "why" something is done a certain way
- Documenting complex algorithms
- Flagging future enhancements (TODO comments)
- Documenting API interfaces
❌ Avoid Comments For:
- Explaining obvious code
- Duplicating what the code already clearly states
- Commenting out unused code (delete it instead)
- Line-by-line explanations
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 · 39 lines · 278 tokens per session scan A 0a525744d617
no-comments is a cursor rule published in the GitHub repository BrainDAO/adk-ts (119 stars, last pushed 2mo ago), licensed MIT. It adds 278 tokens to every session, about $0.0014 per session on Opus 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-30.
Other cursor rules, from other repositories
entity-guard
Entity schema-diff guard for the canonical standalone entity file.
open-mercato
Route every standalone app task through the root agent rules.
generated-guard
Prevent edits to generated application registries.
codegraph
CodeGraph MCP usage guide — when to use which tool.
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-barrel-files
Avoid barrel files and unnecessary re-exports.