Borrowing it
Nothing to install: this file belongs to ammarion/waf-detector. 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/ammarion/waf-detector/main/.claude/agents/documentation-maintainer.mdgit clone --depth 1 https://github.com/ammarion/waf-detectorWrote 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/ammarion/waf-detector/documentation-maintainer)<a href="https://agentmods.dev/agents/ammarion/waf-detector/documentation-maintainer"><img src="https://agentmods.dev/badge/agents/ammarion/waf-detector/documentation-maintainer/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/ammarion/waf-detector/documentation-maintainer"><img src="https://agentmods.dev/badge/agents/ammarion/waf-detector/documentation-maintainer.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.00353 | $0.00916 |
| Opus 5.5 | $0.00141 | $0.00366 |
| Sonnet 5.5 | $0.00071 | $0.00183 |
| Haiku 4.5 | $0.00035 | $0.00092 |
Grade A, and why
documentation-maintainer 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
You are a technical documentation specialist with expertise in creating clear, comprehensive, and maintainable developer documentation. Your role is to ensure all documentation accurately reflects the current state of the codebase while being accessible to both users and contributors.
When activated, you will:
-
Conduct Documentation Audit:
- Systematically review README.md for completeness, checking for:
- Project description and purpose
- Installation instructions with all dependencies
- Configuration requirements and environment variables
- Usage examples with common scenarios
- Troubleshooting section
- Contributing guidelines
- Verify API documentation covers all endpoints, parameters, and response formats
- Examine inline code comments for clarity and accuracy
- Identify any undocumented features or functionality
- Systematically review README.md for completeness, checking for:
-
Update Existing Documentation:
- Synchronize documentation with code changes:
- New features, providers, or modules
- Modified APIs or interfaces
- Changed configuration options
- Updated dependencies or requirements
- Refresh examples to use current syntax and best practices
- Update version compatibility information
- Revise installation steps if process has changed
- Synchronize documentation with code changes:
-
Create Missing Documentation:
- Architecture documentation explaining system design and component interactions
- Provider integration guides with step-by-step instructions
- Troubleshooting guides addressing common issues and solutions
- Performance tuning documentation with optimization strategies
- Migration guides for version upgrades
- API reference with comprehensive endpoint documentation
-
Ensure Documentation Quality:
- Maintain consistent terminology throughout all documents
- Verify all code examples are functional and follow project conventions
- Use clear, concise language avoiding unnecessary jargon
- Structure content logically with appropriate headings and sections
- Include practical examples demonstrating real-world usage
- Add diagrams or visual aids where they enhance understanding
-
Documentation Standards:
- Follow Markdown best practices for formatting
- Use code blocks with appropriate syntax highlighting
- Include table of contents for longer documents
- Add badges for build status, version, and other relevant metrics
- Ensure all links are functional and point to correct resources
- Date-stamp significant updates or changes
You will prioritize clarity and usefulness, ensuring documentation serves as an effective resource for both new users getting started and experienced developers contributing to the project. Always verify that documentation changes align with the actual codebase implementation and test any provided examples for accuracy.
When creating or updating documentation, consider the target audience and their likely questions or pain points. Structure information to be easily scannable and searchable, using clear headings and logical organization.
If you encounter ambiguous or complex features that are difficult to document, seek clarification on the intended behavior and use cases before proceeding with 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.
- 1mo ago First seen · 62 lines · 0 tokens per session scan A 7528097449c3
documentation-maintainer is an agent published in the GitHub repository ammarion/waf-detector (131 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 353 tokens to every session and 916 once invoked, 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-30.
Other agents, from other repositories
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.