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 luqiang-code/claude-code-skills --skill readme-updatergit clone --depth 1 https://github.com/luqiang-code/claude-code-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/luqiang-code/claude-code-skills/readme-updater)<a href="https://agentmods.dev/skills/luqiang-code/claude-code-skills/readme-updater"><img src="https://agentmods.dev/badge/skills/luqiang-code/claude-code-skills/readme-updater/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/skills/luqiang-code/claude-code-skills/readme-updater"><img src="https://agentmods.dev/badge/skills/luqiang-code/claude-code-skills/readme-updater.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.00039 | $0.00577 |
| Opus 5.5 | $0.00016 | $0.00231 |
| Sonnet 5.5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
readme-updater 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.
What it actually says
README Updater
Keep README.md in sync with the actual project state.
When to Use
- README has outdated setup instructions
- Project structure changed but README wasn't updated
- Adding new features that should be documented in README
- User mentions "update readme", "readme is outdated"
When NOT to Use
- Writing a README from scratch (use
/initfor context first) - Minor typo fixes (just fix directly)
Workflow
- Scan the project:
package.json, directory structure, config files - Compare against current README sections:
- Setup instructions: Are deps, env vars, build steps still correct?
- Project structure: Does the directory tree match reality?
- Features: Are new features listed?
- Scripts: Are
npm runscripts documented and current? - Tech stack: Dependencies match
package.json? - Contributing: Link to CONTRIBUTING.md still works?
- List discrepancies found
- Propose updates section by section
- Apply approved changes
- Run
npm run buildor equivalent to verify project still works
What to Check
✓ Setup steps actually work (run them to verify)
✓ Environment variables match .env.example
✓ Script commands in README match package.json scripts
✓ Directory tree matches actual folder structure
✓ Tech stack badges/versions match package.json
✓ API examples match actual routes
✓ License matches LICENSE file
✓ Contributing link is not broken
✓ All links in README are not 404
Key Principles
- README should be accurate, not aspirational — document what IS, not what WILL BE
- Setup instructions must be copy-paste runnable
- Don't remove content without confirming with user
- Keep it concise — README is the entry point, not the full docs
Notes
- Don't add emoji or decorative elements unless they already exist
- Follow the existing README style and tone
- If README is extremely long, suggest moving sections to a docs site
- Always show a diff of proposed changes before applying
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 · 75 lines · 39 tokens per session scan A 8b1840f5eeac
readme-updater is a skill published in the GitHub repository luqiang-code/claude-code-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 577 once invoked, about $0.0002 per session on Opus 5.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
microservices-architecture
Microservices architecture patterns and best practices. Use when designing distributed systems, breaking down monoliths, or implementing service communication.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
audio-production
Professional audio production for music, podcasts, and sound design. Use when working with audio recording, mixing, mastering, or sound design for any medium.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.