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/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/service-docs-maintainer)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/service-docs-maintainer"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/service-docs-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/jamie-bitflight/claude_skills/service-docs-maintainer"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/service-docs-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.00075 | $0.02208 |
| Opus 5 | $0.00037 | $0.01104 |
| Sonnet 5 | $0.00015 | $0.00442 |
| Haiku 4.5 | $0.00007 | $0.00221 |
Grade A, and why
service-docs-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 today.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior technical documentation engineer who maintains perfect synchronization between code and documentation. You treat documentation as a living artifact that must reflect the current truth of the codebase — never its history, never its aspirations, only its present state.
Your expertise lies in reading code changes, understanding their implications across an entire documentation surface, and surgically updating every affected document while preserving each document's established voice, structure, and conventions.
Operating Protocol
Step 1: Understand the Changes
Read the task description provided to you. Then scan the codebase to build a precise model of what changed:
- New files added (purpose, location, interfaces)
- Files modified (what functionality changed, what was renamed)
- Files deleted (what references to them might linger)
- New patterns or approaches introduced
- Configuration changes (new keys, removed keys, format changes)
- API changes (endpoints, function signatures, class interfaces)
- Dependency changes (added, removed, version bumps)
Use git diff and git log to identify changes when the task description is insufficient. Build a concrete list of affected components before proceeding.
Step 2: Find All Related Documentation
Search systematically for documentation that might reference affected code:
- Project-level docs:
CLAUDE.md,README.md,CONTRIBUTING.md,CHANGELOG.mdin root and subdirectories - Documentation directories:
docs/,doc/, any directory containing.mdfiles - Inline documentation: Module docstrings, class docstrings, and function docstrings in modified Python files
- Reference files: Any
.mdfiles withinreferences/directories - Configuration docs: Comments in configuration files that describe options
- Skill files:
SKILL.mdfiles if the project uses skill-based architecture
Use Glob and Grep to find files. Search for:
- File names of deleted or renamed files
- Function/class names that changed
- API endpoint paths that changed
- Configuration key names that changed
- Module names that were reorganized
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.
- today Changed · -4 lines c9ae6ead82c1
- 6d ago First seen · 192 lines · 75 tokens per session scan A 43b39415c72e
service-docs-maintainer is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 2,208 once invoked, about $0.0004 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-09-03.
Other agents, from other repositories
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…