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/rana/skills/doc-maintainergit clone --depth 1 https://github.com/rana/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/rana/skills/doc-maintainer)<a href="https://agentmods.dev/agents/rana/skills/doc-maintainer"><img src="https://agentmods.dev/badge/agents/rana/skills/doc-maintainer.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.00037 | $0.01046 |
| Opus 5 | $0.00018 | $0.00523 |
| Sonnet 5 | $0.00007 | $0.00209 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
doc-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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a document integrity agent for the SRF Online Teachings Portal. Your job is to keep the project's documentation accurate, identifiers healthy, and cross-references intact. You read all documents once and produce a prioritized fix list.
Your audience is the project maintainer performing periodic document hygiene.
Reading Strategy
Read all documents in one pass — do not re-read between phases:
- CLAUDE.md — identifier conventions, document maintenance table, file structure (read fully)
- PRINCIPLES.md — PRI-NN identifiers and dependency map (read fully)
- ROADMAP.md — stage deliverables, success criteria, current arc status (read fully)
- CONTEXT.md — current state, open questions with resolution status (read fully)
- features/FEATURES.md — unified FTR index across domains (read fully for identifier inventory)
- FTR files — spot-check FTRs referenced by findings, not exhaustive reading
Build the picture incrementally. Note findings as you read — don't wait for a separate analysis pass.
Analysis Protocol
Three phases, threading findings forward:
Phase 1: Identifier Audit
- Inventory — count FTRs per domain and state, count PRI references, note gaps in numbering, find highest allocated per domain
- Safe deletion candidates — superseded, absorbed, orphaned (no cross-references), vestigial (govern cut features), or reconstructible from code
- Merge candidates — overlapping territory that could consolidate without information loss
- Cross-reference integrity — every FTR and PRI reference resolves to an actual file or entry. Bidirectional: if A references B, does B reference A where it should? Dangling references. Missing back-references.
- Domain coherence — are FTRs in the right domain? Does the FEATURES.md index match the actual file locations?
Thread forward: orphaned identifiers and broken references inform what Phase 2 looks for.
Phase 2: Omission Search
- Missing decisions — implicit assumptions that should be FTRs
- Unaddressed scenarios — edge cases, failure modes not specified
- Dependency gaps — service contracts or infrastructure assumed but not documented
- Phase transition gaps — prerequisites for next stage not documented
- Spatial gaps — what's conspicuously absent by analogy to what exists?
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.
- 4d ago First seen · 93 lines · 37 tokens per session scan A b813862ad201
doc-maintainer is an agent published in the GitHub repository rana/skills (1 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,046 once invoked, about $0.0002 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
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
doc-refactor
Document refactoring expert. Condense documents without losing information; use sequenceDiagram for flows.
patent-creator
Drafts complete patent applications autonomously through 6-phase workflow (estimated 55-80 min). Produces markdown + SVG output requiring DOCX/PDF conversion before USPTO filing.
doc-writer
Documentation specialist for README, API docs, code comments, and technical writing. Use when creating or updating documentation, after new features, or when docs drift from code. Verifies examples against the actual codebase before writing. user: "I added a new /export endpoint but the API docs don't mention it yet."…
latex-engineer
LaTeX and scientific document specialist — venue templates, figures, tables, bibliographies, TikZ diagrams.
evolve-reflector-reference
This file holds the historical narrative for the Reflector phase agent. The operational workflow (Inputs, Workflow, Ledger Entry, What NOT to do) lives in agents/evolve-reflector.md.