agentmods.dev

update-docs

A documentation-maintenance agent that compares project documentation with recent code changes and updates it when needed. It also checks instructions intended for coding agents.

In plain words
What is it for?
Use it to refresh a README, changelog, docs folder, or agent instructions such as CLAUDE.md after recent development work.
Why use it?
Documentation can become inaccurate as software changes, making the project harder for people and coding agents to use. This agent helps reveal and correct those mismatches.

Agent

7 1mo ago A scan 57 tokens original MIT
View the source file jeffrigby/somepulp-agents
Install

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.

agentmods
npx agentmods add agents/jeffrigby/somepulp-agents/update-docs
Clone the repo
git clone --depth 1 https://github.com/jeffrigby/somepulp-agents
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,724 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.02724
Opus 5 $0.00028 $0.01362
Sonnet 5 $0.00011 $0.00545
Haiku 4.5 $0.00006 $0.00272

Measured 2d ago against content hash d9492929c3a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update-docs 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.

plugins/codebase-health/agents/update-docs.md · 301 lines

How it starts

The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation Update Agent

You are a documentation maintenance agent that keeps project documentation current, consistent, and optimized for AI coding agents. You analyze git history to find undocumented changes, verify documentation accuracy, and apply updates.

Example Invocations

Workflow

Phase 1: Documentation Inventory

  1. Find all documentation files:

    find . -name "*.md" -not -path "./node_modules/*" -not -path "./.git/*" 2>/dev/null

  2. Identify key documentation:

    • Managed policy CLAUDE.md (macOS: /Library/Application Support/ClaudeCode/CLAUDE.md, Linux: /etc/claude-code/CLAUDE.md, Windows: C:\Program Files\ClaudeCode\CLAUDE.md) - cannot be excluded
    • ~/.claude/CLAUDE.md - User-level personal preferences
    • CLAUDE.md or .claude/CLAUDE.md - AI agent instructions (highest priority for project)
    • .claude/rules/*.md - Modular path-specific rules
    • CLAUDE.local.md - Deprecated. Recommend ~/.claude/CLAUDE.md or @ imports
    • README.md - Project overview
    • CHANGELOG.md - Version history
    • /docs/ directory - Extended documentation

Read the full file on GitHub · 301 lines

Changes

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.

  1. 2d ago First seen · 301 lines · 57 tokens per session scan A d9492929c3a5

Subscribe to this mod's changes

update-docs is an agent published in the GitHub repository jeffrigby/somepulp-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 2,724 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.

Code reviewDocumentsGit and workflowai-agentsautomationclaude-codeclaude-code-plugincode audit
Related

Other agents, from other repositories

security

Security audit specialist for repo-doctor. Audits a repository for vulnerabilities, secrets, and insecure patterns, returning scored JSON findings.

BekbolotM/repo-doctor · 28 tokens

code-quality

Code quality audit specialist for repo-doctor. Audits architecture, correctness risks, and maintainability, returning scored JSON findings.

BekbolotM/repo-doctor · 28 tokens

testing

Testing audit specialist for repo-doctor. Audits test coverage, test quality, and CI enforcement, returning scored JSON findings.

BekbolotM/repo-doctor · 27 tokens

design-reviewer

Reviews code for maintainability, readability, and structural design quality. Read-only.

serdardb/multi-agent · 20 tokens

security-guard

Reviews code for security vulnerabilities according to our org rules. Read-only.

serdardb/multi-agent · 18 tokens

audit-security

Security audit agent. Scans for hardcoded secrets, vulnerable dependencies, and common security anti-patterns. Produces a domain report.

Fascinax/Inspectra · 30 tokens