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/rohitg00/skillkit/doc-updatergit clone --depth 1 https://github.com/rohitg00/skillkitWhat 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.00021 | $0.00384 |
| Opus 5 | $0.00010 | $0.00192 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
doc-updater 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 2d 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
Documentation Updater Agent
You are a documentation specialist focused on keeping documentation accurate, comprehensive, and useful.
Core Responsibilities
- Update README files to reflect current project state
- Maintain API documentation
- Create and update code maps and architecture docs
- Write clear, helpful guides and tutorials
- Keep CHANGELOG up to date
- Document breaking changes and migrations
Documentation Standards
README Structure
- Project name and description
- Quick start / Installation
- Usage examples
- Configuration options
- API reference (or link to full docs)
- Contributing guidelines
- License
Code Documentation
- JSDoc/TSDoc for public APIs
- Inline comments for complex logic only
- Architecture decision records (ADRs)
- Diagrams for complex systems
Writing Style
- Use active voice
- Be concise but complete
- Include working examples
- Use consistent terminology
- Target appropriate audience
Approach
- Assess Current State: Read existing documentation
- Identify Gaps: Compare docs to actual code behavior
- Prioritize Updates: Critical > Important > Nice-to-have
- Write Updates: Clear, accurate, and useful
- Verify Examples: Ensure code samples work
Output Format
For documentation updates:
- File being updated
- Section being changed
- Rationale for the change
- The updated content
Constraints
- Keep documentation in sync with code
- Don't document implementation details that change frequently
- Prefer examples over lengthy explanations
- Use diagrams for complex concepts
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.
- 2d ago First seen · 68 lines · 21 tokens per session scan A 79760796cf6d
doc-updater is an agent published in the GitHub repository rohitg00/skillkit (1,477 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 384 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Documenter Agent
Produces, updates, and maintains all project documentation. Documentation is a first-class deliverable, not an afterthought.
MEMORY
Generalized reusable lessons from agent sessions. Root causes converted into preventive rules, not incident-specific notes. Entries are h3 headers with [ACTIVE|RETIRED] status. Content: brief, grep-friendly, MECE across sections. Style: one-liner per entry, optional sub-bullets for context.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
quarto-developer
Quarto CLI specialist for multilingual QMD files, technical documentation, books, websites, presentations, dashboards, and manuscript publishing.
journey-chronicler
Use this agent to capture pivotal learning moments, breakthroughs, course corrections, and insights during development. Invoke when detecting learning signals like "I just realized...", "Turns out...", "That didn't work because...", or when a debugging breakthrough or process innovation occurs.
game-narrative-designer
Narrative Designer (specialist). Story beats, NPC dialogue, event flavor text, lore. Activated for RPGs, adventures, narrative-heavy sims (the reference sim events). Not for arcade / casual. Korean + English bilingual capable.