Borrowing it
Nothing to install: this file belongs to Szesnasty/Jarvis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Szesnasty/Jarvis/main/.claude/skills/update-docs/SKILL.mdgit clone --depth 1 https://github.com/Szesnasty/JarvisWrote 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/szesnasty/jarvis/update-docs)<a href="https://agentmods.dev/skills/szesnasty/jarvis/update-docs"><img src="https://agentmods.dev/badge/skills/szesnasty/jarvis/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.00063 | $0.01968 |
| Opus 5 | $0.00032 | $0.00984 |
| Sonnet 5 | $0.00013 | $0.00394 |
| Haiku 4.5 | $0.00006 | $0.00197 |
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 6d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Workflow
How to Document
You are writing documentation that another developer will read to understand this project. Your goal is to explain why things exist and how they fit together — not to restate what the code already says.
What good documentation looks like
- Summary: 2-3 sentences a developer can read in 10 seconds to know if this feature is relevant to them
- How it works: The architecture at guide level — data flow, key decisions, trade-offs. A developer should understand the design without reading every line of code
- Key files: Each file with a one-line description of its responsibility — not just the filename, but what it does
- API/Interface: Only for features with public exports. Include TypeScript signatures and brief descriptions
- Gotchas: Non-obvious behaviors, surprising edge cases, things that have bitten people before. This is consistently the most valuable section
What bad documentation looks like — do NOT write this
- Restating function names as descriptions ("readRegistry reads the registry")
- Listing exports without explaining what they're for
- Copy-pasting large code blocks instead of referencing file paths
- Revision history, glossaries, or timeline sections
- Vague descriptions ("handles X logic for the application")
Three Entry Points
1. Planning a new feature
Developer says "plan out feature X" or "let's build X":
- Create
docs/features/{name}.mdwith Summary, Definition of Done, Non-goals FIRST - Use this as the planning document — align on scope before writing code
- Fill in How It Works and Key Files as you build
- By the time DoD is checked off, the doc is already written
2. Filling in scaffold docs (after codument scan)
Scan creates doc files with frontmatter and file listings but no content. You are the orchestrator — delegate the actual writing to the doc-writer agent so each feature gets its own focused context window.
Process:
- Read
docs/.registry.jsonto find all entries withstatus: "needs-review" - For each entry, spawn a doc-writer agent with specific instructions:
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.
- 6d ago First seen · 186 lines · 63 tokens per session scan A b0aa22d4b906
update-docs is a skill published in the GitHub repository Szesnasty/Jarvis (10 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,968 once invoked, about $0.0003 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
shodh-memory
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.
create-agent
Skill "create-agent" from PM-Shawn/Abu-Cowork, covering 代理文件格式, 元数据字段说明, 创建流程, 代理类型建议 and 示例对话.
vault
Search, read, write, and manage files in the Kept conversation vault. Use when the user asks about past conversations, wants to save notes, needs to find specific content, or wants to organize their vault.
using-mineecho-skills
技能系统导航。当用户询问"你能做什么"、"有什么功能"、"有什么技能"或不确定如何完成某个任务时，使用此技能列出所有可用技能并建议最合适的技能。此技能是每个对话开始时默认加载的，用于技能发现。.
article-writer
Multi-style article creation skill. Supports 5 writing styles (deep analysis, practical guide, story-driven, opinion, news brief), including complete workflow: material collection → outline → content → formatting. Activated when users mention "write article", "write post", "create", or "draft".
sn-search-academic
用于学术调研、论文精读、相关工作梳理、百科知识查询和引用链追溯。.