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.
git clone --depth 1 https://github.com/HeiSir2014/duckduckgo-mcp-serverWrote 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.
[](https://agentmods.dev/rules/heisir2014/duckduckgo-mcp-server/no-comments)<a href="https://agentmods.dev/rules/heisir2014/duckduckgo-mcp-server/no-comments"><img src="https://agentmods.dev/badge/rules/heisir2014/duckduckgo-mcp-server/no-comments.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $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 6d 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.
This is a copy
100% identical to no-comments — 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.
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.
- 6d ago First seen · 39 lines · 278 tokens per session scan A 0a525744d617
no-comments is a cursor rule published in the GitHub repository HeiSir2014/duckduckgo-mcp-server (3 stars, last pushed 5mo 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. It is 100% identical to no-comments, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.