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 ApexIQ/skillsmith --skill doc_updatergit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/doc_updater)<a href="https://agentmods.dev/skills/apexiq/skillsmith/doc_updater"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/doc_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/apexiq/skillsmith/doc_updater"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/doc_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.00040 | $0.01595 |
| Opus 5 | $0.00020 | $0.00797 |
| Sonnet 5 | $0.00008 | $0.00319 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
doc-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 10d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📝 Doc Updater — Keep Documentation Alive
Philosophy: Stale docs are worse than no docs. Every code change that affects behavior must update the corresponding documentation in the same PR.
1. When to Use This Skill
- After modifying public APIs or CLI commands
- After adding/removing features
- After refactoring that changes file structure or module boundaries
- Before releasing a new version
- When onboarding docs don't match reality
2. The Documentation Sync Checklist
After ANY code change, check these in order:
Tier 1: Must Update (Same PR)
- README.md — Does the quick start still work? Are commands/examples still valid?
- API docs — Did function signatures, parameters, or return types change?
- CLI help text — Did command names, flags, or descriptions change?
- Inline comments — Do comments near changed code still describe truth?
- Error messages — Do error messages reference correct commands/paths?
Tier 2: Should Update (Within Sprint)
- CHANGELOG.md — Is the change logged under the correct version?
- Architecture docs — Did component boundaries or data flow change?
- Configuration docs — Did config options, defaults, or env vars change?
- Migration guides — Is there a breaking change that needs a migration path?
Tier 3: Nice to Update (Backlog)
- Tutorials/guides — Do step-by-step guides still produce correct results?
- FAQ — Are answered questions still accurate?
- Diagrams — Do architecture diagrams reflect current state?
3. Documentation Patterns
Pattern 1: Command Reference Sync
When CLI commands change, update docs systematically:
# Step 1: Generate current command surface
skillsmith --help > /tmp/commands.txt
# Step 2: Compare with documented commands in README
grep -E "^- \`skillsmith" README.md > /tmp/documented.txt
# Step 3: Diff to find drift
diff /tmp/commands.txt /tmp/documented.txt
Pattern 2: API Documentation from Code
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.
- 10d ago First seen · 194 lines · 40 tokens per session scan A 9b4896c7c00a
doc-updater is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,595 once invoked, about $0.0002 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
pptx
Extract text from Microsoft PowerPoint presentations.
xlsx
Extract data from Excel and CSV files.
agent-teams
Multi-agent team orchestration with native Agent Teams. Trigger when the user wants to launch a team of agents, coordinate parallel work with inter-agent communication, or use swarm mode.
ops-infra-code
Infrastructure as Code with Terraform/OpenTofu. Trigger to create modules, configure backends, write idiomatic HCL, or audit infrastructure.
Read, create and manipulate PDF files — extract text and tables, merge, split, rotate, reorder and delete pages, read and fill AcroForm fields, add or strip metadata, encrypt and decrypt, and generate new PDFs from HTML or from scratch. Also covers rasterising pages to images so a PDF can actually be looked at, and…
easd-verify
Run the final EASD integration and evidence gate against accepted AC policies, then prepare a convergence recommendation. Use after implementation and any required independent review; not for task-local code review or ordinary tests outside EASD.