Jarvis: Skill for Claude Code

.claude/skills/update-docs/SKILL.md

update-docs is a skill for Claude Code from Szesnasty/Jarvis. It costs 63 tokens per session (1,968 once invoked), scanned A, original, Apache-2.0.

A workflow for documenting a software project by reading its source code and creating documentation that explains why features exist and how they fit together.

In plain words
What is it for?
Use it to create or update project documentation, explain feature data flows and design decisions, list important files, and record known pitfalls.
Why use it?
It fills documentation gaps and keeps project guides aligned with code changes, including architecture, key files, public interfaces, and non-obvious edge cases.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is Szesnasty/Jarvis's own configuration. It tells Claude Code how to work on Jarvis itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Jarvis configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Szesnasty/Jarvis/main/.claude/skills/update-docs/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Szesnasty/Jarvis

Made for: Claude Code.

Wrote 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.

agentmods badge for update-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/szesnasty/jarvis/update-docs/github.svg)](https://agentmods.dev/skills/szesnasty/jarvis/update-docs)
Your own site
<a href="https://agentmods.dev/skills/szesnasty/jarvis/update-docs"><img src="https://agentmods.dev/badge/skills/szesnasty/jarvis/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.

agentmods 80×15 button for update-docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/szesnasty/jarvis/update-docs"><img src="https://agentmods.dev/badge/skills/szesnasty/jarvis/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,968 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.01968
Opus 5.5 $0.00025 $0.00787
Sonnet 5.5 $0.00013 $0.00394
Haiku 4.5 $0.00006 $0.00197

Measured 1mo ago against content hash b0aa22d4b906, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/skills/update-docs/SKILL.md · 186 lines

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":

  1. Create docs/features/{name}.md with Summary, Definition of Done, Non-goals FIRST
  2. Use this as the planning document — align on scope before writing code
  3. Fill in How It Works and Key Files as you build
  4. 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:

  1. Read docs/.registry.json to find all entries with status: "needs-review"
  2. For each entry, spawn a doc-writer agent with specific instructions:

Read the full file on GitHub · 186 lines

Changes

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.

  1. 1mo ago First seen · 186 lines · 63 tokens per session scan A b0aa22d4b906

Subscribe to this mod's changes

update-docs is a skill published in the GitHub repository Szesnasty/Jarvis (12 stars, last pushed 1mo 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.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.