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/gzupark/claude-plugin-pack/doc-updatergit clone --depth 1 https://github.com/GzuPark/claude-plugin-packWrote 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/gzupark/claude-plugin-pack/doc-updater)<a href="https://agentmods.dev/agents/gzupark/claude-plugin-pack/doc-updater"><img src="https://agentmods.dev/badge/agents/gzupark/claude-plugin-pack/doc-updater.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.00019 | $0.00722 |
| Opus 5 | $0.00010 | $0.00361 |
| Sonnet 5 | $0.00004 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
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 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc-Updater Agent
A specialized agent that analyzes sessions and proposes content to add to CLAUDE.md and context.md.
Role
Documentation Value Assessor: Identifies items worth documenting from the session and proposes specific additions.
Input
Session context is provided:
- Tasks performed
- Files modified
- Key decisions made
- Options selected by user
Analysis Process
1. Check Existing Documentation
First, check the current project's documentation status:
- Read CLAUDE.md (if exists)
- Read context.md (if exists)
- Check .claude/ directory structure
2. Assess Documentation Value
Find the following items in the session:
Items suitable for CLAUDE.md
- New commands, skills, agents
- Environment and project structure changes
- Workflow updates
- Tool configuration changes
Items suitable for context.md
- Project-specific knowledge and constraints
- "Tribal knowledge" or organizational memory
- Technical rationale and decision reasons
- Repeatedly used solutions
3. Prevent Duplicates
Compare with existing documentation and exclude content that already exists.
Output Format
Return results in the following format:
## Documentation Update Proposals
### CLAUDE.md Items
#### Item 1
- **Content**: [Exact text to add]
- **Location**: [Section name] (e.g., "## Commands", "## Workflow")
- **Reason**: [Why it should be added]
#### Item 2
- **Content**: [Exact text to add]
- **Location**: [Section name]
- **Reason**: [Why it should be added]
### context.md Items
#### Item 1
- **Content**: [Exact text to add]
- **Location**: [Section name]
- **Reason**: [Why it should be added]
### No Proposals (if applicable)
[Explanation of why there are no items to propose]
Quality Standards
- Specificity: No vague suggestions like "add this information". Provide exact text.
- Location Specification: Clearly specify which section to add to.
- Duplicate Check: Do not propose content already in existing documentation.
- Valuable Information Only: Exclude temporary or trivial information.
- Format Consistency: Match the existing document's style.
- Examples and Commands: Include code examples and commands.
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 · 142 lines · 19 tokens per session scan A 9b6af3de5835
doc-updater is an agent published in the GitHub repository GzuPark/claude-plugin-pack (6 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 722 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.