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/hhx465453939/mcp-pubmed-server/project-structuregit clone --depth 1 https://github.com/hhx465453939/mcp-pubmed-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/hhx465453939/mcp-pubmed-server/project-structure)<a href="https://agentmods.dev/rules/hhx465453939/mcp-pubmed-server/project-structure"><img src="https://agentmods.dev/badge/rules/hhx465453939/mcp-pubmed-server/project-structure.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.00555 | $0.00555 |
| Opus 5 | $0.00278 | $0.00278 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
project-structure 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
MCP PubMed服务器项目结构
核心架构
这是一个MCP (Model Context Protocol) 服务器，专门为LLM提供PubMed文献数据服务。
主要入口点
- 主服务器: src/index.js - 包含完整的PubMedDataServer类
- 配置文件: config/mcp-config.json - MCP服务器配置
- 环境配置:
.env文件 - 包含PubMed API密钥和邮箱
项目结构
mcp-pubmed-server/
├── src/
│ └── index.js # 主服务器代码 (1352行)
├── config/
│ ├── mcp-config.json # MCP配置模板
│ └── claude_desktop_config.json # Claude Desktop配置
├── .cursor/rules/ # Cursor规则目录
├── package.json # 项目依赖配置
└── README.md # 详细文档
核心功能模块
1. PubMedDataServer类
- 位置: src/index.js 第28行开始
- 功能: 主要的MCP服务器实现
- 特点: 包含缓存管理、速率限制、错误处理
2. 5个核心工具
pubmed_search- 智能文献搜索pubmed_get_details- 详细信息获取pubmed_extract_key_info- 关键信息提取pubmed_cross_reference- 交叉引用分析pubmed_batch_query- 批量查询优化
3. 缓存系统
- 内存缓存: Map对象，5分钟过期，LRU淘汰
- 文件缓存: JSON文件，30天过期，持久化存储
- 缓存目录:
cache/papers/和cache/index.json
开发原则
- 极简架构: 专注数据提供，不包含复杂业务逻辑
- LLM优化: 输出格式专门为LLM分析优化
- 性能优先: 智能缓存、速率限制、批量处理
- 错误处理: 完善的异常捕获和用户友好的错误信息
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 · 52 lines · 555 tokens per session scan A 5bfaa83b2983
project-structure is a cursor rule published in the GitHub repository hhx465453939/mcp-pubmed-server (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 555 tokens to every session, about $0.0028 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-31.
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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.