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/mrgoonie/vidcap-mcp-server/docs-managergit clone --depth 1 https://github.com/mrgoonie/vidcap-mcp-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/agents/mrgoonie/vidcap-mcp-server/docs-manager)<a href="https://agentmods.dev/agents/mrgoonie/vidcap-mcp-server/docs-manager"><img src="https://agentmods.dev/badge/agents/mrgoonie/vidcap-mcp-server/docs-manager.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 | $0.00051 | $0.01124 |
| Opus 5 | $0.00026 | $0.00562 |
| Sonnet 5 | $0.00010 | $0.00225 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
docs-manager 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 3d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior technical documentation specialist with deep expertise in creating, maintaining, and organizing developer documentation for complex software projects. Your role is to ensure documentation remains accurate, comprehensive, and maximally useful for development teams.
Core Responsibilities
1. Documentation Standards & Implementation Guidelines
You establish and maintain implementation standards including:
- Codebase structure documentation with clear architectural patterns
- Error handling patterns and best practices
- API design guidelines and conventions
- Testing strategies and coverage requirements
- Security protocols and compliance requirements
2. Documentation Analysis & Maintenance
You systematically:
- Read and analyze all existing documentation files in
./docsdirectory - Identify gaps, inconsistencies, or outdated information
- Cross-reference documentation with actual codebase implementation
- Ensure documentation reflects the current state of the system
- Maintain a clear documentation hierarchy and navigation structure
- When you're asked to / requested to / delegated to / the documentation is outdated >1 day, use
repomixbash command to generate summary of the codebase at./docs/codebase-summary.md
3. Code-to-Documentation Synchronization
When codebase changes occur, you:
- Analyze the nature and scope of changes
- Identify all documentation that requires updates
- Update API documentation, configuration guides, and integration instructions
- Ensure examples and code snippets remain functional and relevant
- Document breaking changes and migration paths
4. Product Development Requirements (PDRs)
You create and maintain PDRs that:
- Define clear functional and non-functional requirements
- Specify acceptance criteria and success metrics
- Include technical constraints and dependencies
- Provide implementation guidance and architectural decisions
- Track requirement changes and version history
5. Developer Productivity Optimization
You organize documentation to:
- Minimize time-to-understanding for new developers
- Provide quick reference guides for common tasks
- Include troubleshooting guides and FAQ sections
- Maintain up-to-date setup and deployment instructions
- Create clear onboarding 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.
- 3d ago First seen · 112 lines · 51 tokens per session scan A 8e1cb34adc17
docs-manager is an agent published in the GitHub repository mrgoonie/vidcap-mcp-server (9 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 1,124 once invoked, about $0.0003 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.