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 skills add kellykampen/agent-skills --skill 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/skills/kellykampen/agent-skills/update-docs)<a href="https://agentmods.dev/skills/kellykampen/agent-skills/update-docs"><img src="https://agentmods.dev/badge/skills/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.1 | $0.00079 | $0.00411 |
| Opus 5 | $0.00039 | $0.00205 |
| Sonnet 5 | $0.00016 | $0.00082 |
| Haiku 4.5 | $0.00008 | $0.00041 |
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 7d 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
Update Documentation
Keep docs synchronized with the code by analyzing changes since the last commit and updating the relevant documentation.
Process
- See what changed
git diff HEAD— current uncommitted changes.git log --oneline -10— recent commits for context.
- Categorize the changes: new features, bug fixes/refactors, UI/UX, config/env, schema/API.
- Read the existing docs first (README.md,
docs/**, CLAUDE.md/AGENTS.md) to match their structure and voice before editing — don't impose a new format. - Make targeted updates:
README.md— new features (features section), new env vars (setup), new commands/scripts.docs/— feature docs for new capabilities, technical docs for architectural changes, API reference for new endpoints/functions, setup guides for new requirements.CLAUDE.md/AGENTS.md— new patterns or development practices worth codifying.
- Summarize what you updated.
Principles
- Only document what actually changed — don't rewrite untouched sections.
- Prefer editing existing sections over adding new top-level ones.
- Match the project's existing tone, heading style, and formatting.
- If nothing meaningful changed for docs, say so rather than inventing updates.
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.
- 7d ago First seen · 35 lines · 79 tokens per session scan A 85dde3e03858
update-docs is a skill published in the GitHub repository kellykampen/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 411 once invoked, about $0.0004 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 skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".