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/kellykampen/agent-skills/update-docsgit clone --depth 1 https://github.com/kellykampen/agent-skillsWrote 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/commands/kellykampen/agent-skills/update-docs)<a href="https://agentmods.dev/commands/kellykampen/agent-skills/update-docs"><img src="https://agentmods.dev/badge/commands/kellykampen/agent-skills/update-docs.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.00009 | $0.00472 |
| Opus 5 | $0.00005 | $0.00236 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
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 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Documentation Command
Analyze changes since the last git commit and update README.md and relevant documentation files in the /docs/ directory to reflect new features, improvements, and architectural changes.
What this command does
- Analyzes git changes - Examines git diff and recent commits to identify what has changed
- Identifies documentation gaps - Determines what new features or changes need documentation
- Updates README.md with:
- New features in the Key Features section
- Updated environment variables in setup sections
- New commands or scripts if added
- Updates relevant documentation in
/docs/directories:- Feature documentation for new capabilities
- Technical documentation for architectural changes
- API reference for new endpoints or functions
- Guides for new setup requirements
- Updates CLAUDE.md if there are new patterns or development practices
Command Execution
The command will:
- First run
git diff HEADto see current uncommitted changes - Check
git log --oneline -10for recent commit messages to understand recent development - Analyze the codebase changes to categorize them into:
- New features
- Bug fixes and refactoring
- UI/UX improvements
- Configuration or environment changes
- Database schema changes
- Read current README.md and documentation files to understand existing structure
- Make targeted updates to keep documentation current and accurate
- Provide a summary of what was updated
Usage:
/update-docs
This command requires no arguments and will automatically detect and document changes since the last git commit.
Example Output:
After running, you'll see updates to:
- README.md (if new features were added)
- docs/features/ (for new feature documentation)
- docs/technical/ (for architectural changes)
- CLAUDE.md (for new development patterns)
The command ensures your documentation stays synchronized with your codebase evolution.
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 · 68 lines · 9 tokens per session scan A 904b2f4e431d
update-docs is a command published in the GitHub repository kellykampen/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 472 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.