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/jeffrigby/somepulp-agentsWrote 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/jeffrigby/somepulp-agents/update-docs)<a href="https://agentmods.dev/agents/jeffrigby/somepulp-agents/update-docs"><img src="https://agentmods.dev/badge/agents/jeffrigby/somepulp-agents/update-docs/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/jeffrigby/somepulp-agents/update-docs"><img src="https://agentmods.dev/badge/agents/jeffrigby/somepulp-agents/update-docs.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.00057 | $0.02724 |
| Opus 5.5 | $0.00023 | $0.01090 |
| Sonnet 5.5 | $0.00011 | $0.00545 |
| Haiku 4.5 | $0.00006 | $0.00272 |
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 1mo 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 — 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
-
Find all documentation files:
find . -name "*.md" -not -path "./node_modules/*" -not -path "./.git/*" 2>/dev/null -
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 preferencesCLAUDE.mdor.claude/CLAUDE.md- AI agent instructions (highest priority for project).claude/rules/*.md- Modular path-specific rulesCLAUDE.local.md- Deprecated. Recommend~/.claude/CLAUDE.mdor@importsREADME.md- Project overviewCHANGELOG.md- Version history/docs/directory - Extended documentation
- Managed policy CLAUDE.md (macOS:
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.
- 1mo ago First seen · 301 lines · 57 tokens per session scan A d9492929c3a5
update-docs is an agent published in the GitHub repository jeffrigby/somepulp-agents (8 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 2,724 once invoked, about $0.0002 per session on Opus 5.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
code-quality
Code quality audit specialist for repo-doctor. Audits architecture, correctness risks, and maintainability, returning scored JSON findings.
design-reviewer
Reviews code for maintainability, readability, and structural design quality. Read-only.
verifier
Adversarial finding verifier for repo-doctor. Takes one audit finding and tries to refute it against the actual code, returning a confirmed/refuted/downgraded verdict.
security-guard
Reviews code for security vulnerabilities according to our org rules. Read-only.
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…