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 commands/jeffrigby/somepulp-agents/update-docsgit clone --depth 1 https://github.com/jeffrigby/somepulp-agentsWhat 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.00009 | $0.00170 |
| Opus 5 | $0.00005 | $0.00085 |
| Sonnet 5 | $0.00002 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
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.
What it actually says
Use the update-docs agent to analyze recent code changes and propose documentation updates.
Workflow:
- Launch the update-docs agent to analyze git history, apply routine low-risk fixes, and return a proposed-updates plan for any significant changes
- Review the returned plan and confirm significant changes with the user (via AskUserQuestion) before applying them
- Apply the approved updates
This will:
- Analyze git history for undocumented changes
- Update CLAUDE.md to reflect current patterns and conventions
- Sync README with current project state
- Add CHANGELOG entries for recent changes
- Optimize documentation for AI agent consumption
Scope and time range: $ARGUMENTS
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 · 22 lines · 9 tokens per session scan A 78c232cf5f52
update-docs is a command published in the GitHub repository jeffrigby/somepulp-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 170 once invoked, about $0.0000 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 commands, from other repositories
audit
Run one selected Whats.Going.On. reviewer, or all selected reviewers in dependency waves.
operationalize
Turn an approved synthesis into explicitly untested, source-linked operator aids without executing procedures or changing systems.
cost
Produce a reconciled API-equivalent cost estimate for a completed Whats.Going.On. audit.
summarize
Reconcile completed Whats.Going.On. reviewers and create decision-grade audience reports.
upload
Verify a completed public WGO audit and open a draft PR in the configured report repository.
audit
Full project audit with Health Score, findings, and a prioritized fix plan.