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/loulanyue/awesome-claude-notesWrote 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/loulanyue/awesome-claude-notes/update-docs)<a href="https://agentmods.dev/commands/loulanyue/awesome-claude-notes/update-docs"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/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/commands/loulanyue/awesome-claude-notes/update-docs"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/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.00005 | $0.00309 |
| Opus 5.5 | $0.00002 | $0.00124 |
| Sonnet 5.5 | $0.00001 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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.
This is a copy
100% identical to update-docs — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Update Docs Command
Update documentation to reflect recent changes: $ARGUMENTS
Your Task
- Identify changed code -
git diff --name-only - Find related docs - README, API docs, guides
- Update documentation - Keep in sync with code
- Verify accuracy - Docs match implementation
Documentation Types
README.md
- Installation instructions
- Quick start guide
- Feature overview
- Configuration options
API Documentation
- Endpoint descriptions
- Request/response formats
- Authentication details
- Error codes
Code Comments
- JSDoc for public APIs
- Complex logic explanations
- TODO/FIXME cleanup
Guides
- How-to tutorials
- Architecture decisions (ADRs)
- Troubleshooting guides
Update Checklist
- README reflects current features
- API docs match endpoints
- JSDoc updated for changed functions
- Examples are working
- Links are valid
- Version numbers updated
Documentation Quality
Good Documentation
- Accurate and up-to-date
- Clear and concise
- Has working examples
- Covers edge cases
Avoid
- Outdated information
- Missing parameters
- Broken examples
- Ambiguous language
IMPORTANT: Documentation should be updated alongside code changes, not as an afterthought.
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 · 68 lines · 5 tokens per session scan A 2a036d2ed5b6
update-docs is a command published in the GitHub repository loulanyue/awesome-claude-notes (271 stars, last pushed 17d ago), licensed MIT. It adds 5 tokens to every session and 309 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to update-docs, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.