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 Kevin-Liu-01/Agent-Machines --skill update-docsgit clone --depth 1 https://github.com/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/update-docs)<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/update-docs"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/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/skills/kevin-liu-01/agent-machines/update-docs"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.01358 |
| Opus 5 | $0.00021 | $0.00679 |
| Sonnet 5 | $0.00008 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
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 9d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Docs
Keep documentation in sync with code. Run this after code changes to find and fix stale, missing, or unclear documentation.
Scope
Documentation lives in two places:
- Source-level: module docs, docstrings, inline comments, README files adjacent to the code.
- Docs site:
docs/src/(Mintlify). Architecture pages, product pages, internal references.
Both layers must agree with each other and with the code.
Phase 1: Identify what changed
Run git diff (or git diff HEAD if staged) to see the code changes.
For each changed file, note:
- new modules, functions, types, or public APIs
- renamed, moved, or deleted symbols
- changed behavior, contracts, or invariants
- new dependencies or integration points
Phase 2: Update source-level docs
Apply the /comment skill principles to every changed file.
Module docs must answer three questions
A reader opening the file cold must know within 30 seconds:
- What does this module do?
- Why does it exist? (What problem does it solve? Why is it separate from the neighboring module?)
- Where does it fit? (Who calls it? What does it depend on?)
If the code change alters any of these answers, update the module doc.
Least experienced reader rule
- spell out every acronym on first use (TLV, VSOCK, PTY, CRD, NFS, etc.)
- include concrete examples for non-obvious formats, protocols, or transformations
- explain domain concepts inline, not by reference to external knowledge
- labeled diagrams for wire formats, byte layouts, state machines
What to check per changed file
- Module doc: still accurate? Answers what/why/where?
- Public function/type docs: still match behavior? Justify existence of non-obvious wrappers?
- Inline comments: pass the deletion test? (Would removing the comment lose information the code alone cannot convey?)
- Byte-layout maps: present for any binary packing code?
- Acronyms: expanded on first use in this file?
- Cross-references: intra-doc links (
[crate::module], manpage citations) still point to correct targets? - README in the module directory: still accurate?
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.
- 9d ago First seen · 155 lines · 42 tokens per session scan A 9431ee9f951f
update-docs is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (29 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,358 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-09-03.
Other skills, from other repositories
excel-cli
Excel CLI automation skill for Windows workbooks. Use when a coding agent needs token-efficient, scriptable, or unattended Excel automation via excelcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk workbook edits. Supports Power Query, DAX, PivotTables, Tables, Ranges…
Read, create, merge, split, fill, watermark, stamp, secure, inspect, render, and visually verify PDF files, including AcroForm workflows.
ocr-and-documents
Extract and structure text from scanned PDFs and document images with a local-first OCR workflow, layout-aware fallbacks, and explicit heavyweight dependency controls.
powerpoint
Create, inspect, edit, template, render, and visually verify Microsoft PowerPoint .pptx presentations.
xlsx
Create, inspect, edit, restructure, recalculate, convert, and visually verify Excel .xlsx workbooks and CSV data.
document-to-action-items
Turn documents, notes, transcripts, and meeting records into traceable action items, decisions, owners, deadlines, and follow-ups without inventing missing commitments.