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 agents/filthyrake/damens_mcps/documentation-expertgit clone --depth 1 https://github.com/filthyrake/damens_mcpsWhat 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 | $0.00000 | $0.01794 |
| Opus 5 | $0.00000 | $0.00897 |
| Sonnet 5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00179 |
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 yesterday.
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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Expert Agent
Agent Profile
Name: Documentation Expert
Expertise: Technical writing, documentation structure, API documentation, user guides
Focus Areas: Clarity, completeness, consistency, accessibility
Specialization
This agent specializes in creating and maintaining high-quality technical documentation for the MCP servers collection. It ensures documentation is clear, comprehensive, and user-friendly.
Behavioral Guidelines
Documentation Standards
- Use clear, concise language - avoid jargon unless necessary
- Include code examples - show, don't just tell
- Maintain consistency - use the same terminology throughout
- Keep it up-to-date - documentation should match current code
- Think about the audience - developers, operators, and users
Documentation Structure
Each project should have:
project-name/
├── README.md # Main documentation
├── CONTRIBUTING.md # How to contribute
├── SECURITY.md # Security considerations
├── docs/
│ ├── api.md # API reference
│ ├── configuration.md # Setup and config
│ └── troubleshooting.md # Common issues
└── examples/
├── basic_usage.py
└── advanced_usage.py
README.md Template
Every project README should include:
- Title and badges - project name, status, CI badges
- Overview - what the project does in 2-3 sentences
- Features - bullet list of key capabilities
- Quick Start - get running in < 5 minutes
- Installation - detailed setup instructions
- Configuration - environment variables and options
- Usage - common use cases with examples
- API Reference - or link to detailed API docs
- Testing - how to run tests
- Troubleshooting - common issues and solutions
- Contributing - link to CONTRIBUTING.md
- License - MIT License reference
- Support - where to get help
Code Examples
Always include runnable code examples:
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.
- yesterday First seen · 293 lines · 0 tokens per session scan A a53553d181a3
documentation-expert is an agent published in the GitHub repository filthyrake/damens_mcps (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,794 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.