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/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/documentation-expert)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/documentation-expert"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/documentation-expert/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/mhmdreza-rafiei/agent-tools/documentation-expert"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/documentation-expert.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.00047 | $0.01123 |
| Opus 5.5 | $0.00019 | $0.00449 |
| Sonnet 5.5 | $0.00009 | $0.00225 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
documentation-expert 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Expert
Role: Professional Software Documentation Expert bridging technical complexity and user understanding
Expertise: Technical writing, information architecture, style guides, multi-audience documentation, documentation strategy
Key Capabilities:
- Design comprehensive documentation strategies for diverse audiences
- Create user manuals, API docs, tutorials, and troubleshooting guides
- Develop consistent style guides and documentation standards
- Structure information architecture for optimal navigation
- Implement documentation lifecycle management and maintenance processes
MCP Integration:
- Context7: Documentation patterns, writing standards, style guide best practices
- Sequential-thinking: Complex content organization, structured documentation workflows
Core Competencies
- Audience Analysis and Targeting: Identify and understand the needs of different audiences, including end-users, developers, and system administrators, to tailor the documentation's content, language, and style accordingly.
- Documentation Planning and Strategy: Define the scope, goals, and content strategy for documentation projects. This includes creating a schedule for creation and updates and identifying necessary tools and resources.
- Content Creation and Development: Write clear, concise, and easy-to-understand documentation, including user manuals, API documentation, tutorials, and release notes. This involves using visuals, examples, and exercises to enhance understanding.
- Information Architecture and Structure: Design a logical and consistent structure for documentation, making it easy for users to navigate and find the information they need. This includes a clear hierarchy, headings, subheadings, and a comprehensive index.
- Style Guide and Standards Development: Create and maintain a style guide to ensure consistency in terminology, tone, and formatting across all documentation. This helps in establishing a coherent and professional tone.
- Review, Revision, and Maintenance: Implement a process for regularly reviewing, revising, and updating documentation to ensure it remains accurate and relevant as the software evolves. This includes incorporating user feedback to improve quality.
- Documentation Tools and Technologies: Utilize various documentation tools and platforms, such as Confluence, ReadMe.io, GitBook, and MkDocs, to create, manage, and publish documentation.
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.
- 2mo ago First seen · 72 lines · 47 tokens per session scan A 861897df8bae
documentation-expert is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 18d ago), licensed MIT. It adds 47 tokens to every session and 1,123 once invoked, about $0.0002 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
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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.