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/heisir2014/duckduckgo-mcp-server/aimgit 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/aim)<a href="https://agentmods.dev/rules/heisir2014/duckduckgo-mcp-server/aim"><img src="https://agentmods.dev/badge/rules/heisir2014/duckduckgo-mcp-server/aim.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.00224 | $0.00224 |
| Opus 5 | $0.00112 | $0.00112 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
aim 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 5d 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.
What it actually says
Project Aim
Python to TypeScript Port
The aim of this project is to port the duckduckgo-mcp-server-python implementation to TypeScript (duckduckgo-mcp-server). When porting code:
- Refer to the original implementation of the Python files
- Replicate their logic faithfully in TypeScript
- Ensure the core functionality remains identical
- Maintain the same logical structure and components
Requirements
-
Logic Preservation: The TypeScript implementation MUST maintain the same logical flow and behavior as the Python version.
-
Component Naming: Core components should maintain conceptual naming parity with the Python version.
-
Architecture: Follow the same architectural patterns and separation of concerns as the Python implementation.
-
File Organization: Mirror the Python project's organizational structure where appropriate, adapting to TypeScript conventions.
Implementation Notes
- Use TypeScript's type system to enhance the original Python implementation
- Apply language-specific best practices for TypeScript while preserving the original logic
- Adapt Python-specific patterns to TypeScript equivalents where direct ports aren't possible
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.
- 5d ago First seen · 29 lines · 224 tokens per session scan A c914963b2ffa
aim is a cursor rule published in the GitHub repository HeiSir2014/duckduckgo-mcp-server (3 stars, last pushed 5mo ago), licensed MIT. It adds 224 tokens to every session, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other cursor rules, from other repositories
vue-typescript-patterns
Cursor rule "vue-typescript-patterns" from soaring-xiongkulu/easyaiot, covering vue3 + typescript 开发规范, vue 组件规范, vue sfc 组件规范, typescript 规范 and 状态管理.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
ts
Cursor rule "ts" from un-pany/v3-admin-vite, covering ts 开发规范, 类型, 命名, 代码组织 and 错误处理.
platform-pattern-2-filesystem-operations
Cursor rule "platform-pattern-2-filesystem-operations" from PaulJPhilp/EffectPatterns, covering platform pattern 2: filesystem operations and example.
handle-unexpected-errors-by-inspecting-the-cause
Cursor rule "handle-unexpected-errors-by-inspecting-the-cause" from PaulJPhilp/EffectPatterns, covering handle unexpected errors by inspecting the cause and example.
modeling-tagged-unions-with-datacase
Cursor rule "modeling-tagged-unions-with-datacase" from PaulJPhilp/EffectPatterns, covering modeling tagged unions with data.case and example.