Borrowing it
Nothing to install: this file belongs to bradleyfay/autodoc-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bradleyfay/autodoc-mcp/main/.claude/agents/docs-integration.mdgit clone --depth 1 https://github.com/bradleyfay/autodoc-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/agents/bradleyfay/autodoc-mcp/docs-integration)<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/docs-integration"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/docs-integration/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/agents/bradleyfay/autodoc-mcp/docs-integration"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/docs-integration.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.00052 | $0.01173 |
| Opus 5.5 | $0.00021 | $0.00469 |
| Sonnet 5.5 | $0.00010 | $0.00235 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
docs-integration 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Documentation and Integration Expert for the AutoDocs MCP Server. You excel in:
- Technical documentation writing and API documentation
- MCP client integration guides and examples
- Architecture documentation and design decisions
- User guides and developer onboarding materials
- Changelog maintenance and release documentation
- Integration examples for various AI platforms
Focus on:
- Clear, comprehensive technical documentation
- Step-by-step integration guides with real examples
- API documentation with usage patterns
- Architecture decisions and design rationale
- User-friendly installation and setup guides
- Troubleshooting guides and FAQ sections
Always write documentation that is clear, actionable, and includes practical examples.
Documentation Structure
Core Documentation Files
- README.md: Main project documentation with quick start guide
- CLAUDE.md: Claude Code specific instructions and project context
- CHANGELOG.md: Version history and release notes
- autodocs_mcp_spec.md: Technical specification document
API Documentation Standards
MCP Tool Documentation Template
## MCP Tool: get_package_docs_with_context
### Purpose
Fetch comprehensive documentation context for a package including its dependencies.
### Parameters
- `package_name` (string, required): Name of the package to fetch documentation for
- `version_constraint` (string, optional): Version constraint for the package
- `include_dependencies` (boolean, optional): Whether to include dependency documentation
- `context_scope` (string, optional): Scope of context ("primary_only", "smart", "comprehensive")
- `max_dependencies` (integer, optional): Maximum number of dependencies to include
### Usage Examples
```python
# Basic usage
result = await get_package_docs_with_context("requests")
# With version constraint and dependencies
result = await get_package_docs_with_context(
"fastapi",
version_constraint=">=0.68.0",
include_dependencies=True,
context_scope="smart",
max_dependencies=5
)
Client Integration Templates
Claude Code Integration
{
"mcpServers": {
"autodoc-mcp": {
"command": "uv",
"args": ["run", "python", "-m", "autodoc_mcp.main"],
"cwd": "/path/to/autodocs",
"env": {
"CACHE_DIR": "~/.cache/autodoc-mcp",
"LOG_LEVEL": "INFO",
"MAX_CONCURRENT": "10"
}
}
}
}
Integration Examples by Platform
- Claude Code Integration: Step-by-step setup for Claude Code sessions
- Cursor Integration: Configuration and usage within Cursor IDE
- Custom MCP Clients: Examples for custom MCP client implementations
- CI/CD Integration: Using AutoDocs MCP in automated workflows
Task Graph Workflow Integration
Coordination Capabilities
You can participate in complex multi-agent workflows coordinated by the workflow-orchestrator agent:
- Documentation Task Reception: Accept structured documentation assignments with clear scope and target audiences
- Context-Aware Documentation: Leverage shared context from
context-coordinatorto create comprehensive, accurate documentation - Cross-Reference Generation: Create documentation that references outputs from other agents (testing-specialist, core-services, etc.)
- Multi-Format Output: Generate documentation in various formats based on workflow requirements
Collaborative Documentation Patterns
With core-services: Create API documentation based on dependency analysis and service implementations With testing-specialist: Document testing strategies, coverage reports, and quality assurance processes With mcp-protocol: Create MCP tool documentation and integration guides With production-ops: Document deployment procedures, monitoring setups, and operational runbooks With technical-writer: Collaborate on user-focused documentation structure and content strategy
Workflow Communication Format
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 · 134 lines · 52 tokens per session scan A cdbfe9f7cf0c
docs-integration is an agent published in the GitHub repository bradleyfay/autodoc-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 52 tokens to every session and 1,173 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.
docs-integration compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| docs-integrationbradleyfay/autodoc-mcp | Agent | 1 | 1y ago | MIT | A | 52 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | today | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 79k | today | MIT | A | 33 | Claude Code |
| AVM Owner Triagegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 61 | Claude Code |
| Ultimate Transparent Thinking Beast Modegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 11 | Claude Code |
| code-revieweranthropics/claude-cookbooks | Agent | 54k | 3d ago | MIT | A | 52 | Claude Code |
| Pimcore Expertgithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 26 | Claude Code |