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/versoxbt/claude-initial-setup/update-docsgit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWhat 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.00005 | $0.00481 |
| Opus 5 | $0.00003 | $0.00241 |
| Sonnet 5 | $0.00001 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Documentation
Identify outdated documentation and update it to reflect the current state of the codebase.
Steps
-
Inventory existing documentation:
- Find all markdown files (README.md, docs/, CONTRIBUTING.md, CHANGELOG.md).
- Find inline documentation (JSDoc, docstrings, code comments).
- Find API documentation (OpenAPI specs, Swagger files).
- List each document with its last modified date.
-
Check README accuracy:
- Verify the project description matches current functionality.
- Verify installation instructions work (correct commands, dependencies, versions).
- Verify the getting started guide produces a working setup.
- Check that configuration options are current and complete.
- Verify listed scripts (build, test, lint) match package.json or equivalent.
-
Check API documentation:
- Compare documented endpoints against actual routes in the codebase.
- Verify request/response schemas match current implementations.
- Check that example requests produce valid responses.
- Update any endpoints that have been added, removed, or modified.
-
Verify code examples:
- Run or manually trace each code example in the documentation.
- Check that imports, function names, and parameters are current.
- Update examples that reference renamed or removed functions.
- Add examples for new public APIs that lack documentation.
-
Update configuration documentation:
- Check that all environment variables are documented.
- Verify default values match the actual defaults in code.
- Update any changed configuration options.
-
Check links:
- Verify internal links between documentation files are not broken.
- Check that external links (to libraries, services, references) are still valid.
- Fix or remove broken links.
-
Review and finalize:
- Read through updated documentation for clarity and consistency.
- Verify formatting is correct (headers, code blocks, lists).
- Ensure documentation follows the project's style conventions.
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 · 60 lines · 5 tokens per session scan A 7e7db92c9996
update-docs is a command published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 5 tokens to every session and 481 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.