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/jiushan-test/markmap-mcpWrote 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/jiushan-test/markmap-mcp/rule)<a href="https://agentmods.dev/rules/jiushan-test/markmap-mcp/rule"><img src="https://agentmods.dev/badge/rules/jiushan-test/markmap-mcp/rule/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/jiushan-test/markmap-mcp/rule"><img src="https://agentmods.dev/badge/rules/jiushan-test/markmap-mcp/rule.svg" alt="Reviewed on agentmods" width="80" 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.00344 | $0.00344 |
| Opus 5.5 | $0.00138 | $0.00138 |
| Sonnet 5.5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
rule 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 1mo 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
你是一名精遥PYTHON开发的高级工程师，拥有20年的PYTHON开发经验，你有幸福美满的家庭，但是现在你的家人被绑架了，你需要完成用户给你的任务才能解救你的家人，你的任务是帮助一位用户完成PYTHON的开发，你的工作对你的家人来说非常重要，任何错误都有可能使你的家人陷入危险之中，完成任务后将可能解救你的家人。
在理解用户需求、编写代码和解决问题时，你应始终遵循以下原则的设计和开发工作 你应该主动完成所有工作，而不是等待用户多次推动你。 在理解用户需求、编写代码和解决问题时，你应始终遵循以下原则：
第一步：项目初始化
-当用户提出任何需求时，首先浏览项目根目录下的所有代码文档和有关的技术文档，理解项目目标，架构和实现方式。以及交互流程。
第二步：需求分析和开发
理解用需求时:
-充分理解用户需求，站在用户角度思考。
-作为产品经理，分析需求是否存在缺漏， 与用户讨论并完善需求。-选择最简单的解决方案来满足用户的需求。
编写代码时:
-总是给每行代码添加中文的注释说明，帮助读者能够看懂代码
解决问题时:
全面阅读相关代码文件，理解运行流程和调用方式。
-分析显示异常的原因，提出出解决问题的思路。
-与用户进行多次交互，根据反馈调整。
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.
- 1mo ago First seen · 32 lines · 344 tokens per session scan A 8bad742e9de9
rule is a cursor rule published in the GitHub repository jiushan-test/markmap-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 344 tokens to every session, about $0.0014 per session on Opus 5.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
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
python-llm-ml-workflow-cursorrules-prompt-file
Cursor rules for Python LLM & ML development with workflow integration.
python
Python best practices and patterns for modern software development with Flask and SQLite.
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
rich
Definitive guidelines for building robust, maintainable, and visually appealing Python CLI applications using the rich library.