update-docs

A skill for updating AGENTS.md files with useful lessons learned during development. AGENTS.md files store project instructions, conventions, commands, and architectural notes for coding agents.

In plain words
What is it for?
Use it after learning a project pattern, required command, convention, or common problem. It helps review existing guidance and update the root or package-level documentation.
Why use it?
It prevents important discoveries and recurring pitfalls from being forgotten after a session ends. It also places each note at the appropriate level of the project.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/saffron-health/opencode-gui/update-docs
Any agent
npx skills add saffron-health/opencode-gui --skill update-docs
Clone the repo
git clone --depth 1 https://github.com/saffron-health/opencode-gui

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 234 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% copy Near-identical to another mod 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 $0.00031 $0.00234
Opus 5 $0.00015 $0.00117
Sonnet 5 $0.00006 $0.00047
Haiku 4.5 $0.00003 $0.00023

Measured 2d ago against content hash 1c87170d5130, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

Origin

This is a copy

91% identical to update-docs — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/update-docs/SKILL.md · 30 lines

What it actually says

Update AGENTS.md files based on what was learned in this session about: $TOPIC

Read docs/updating-agents-docs.md for full guidelines before proceeding.

Process

  1. Review the conversation for learnings about the specified topic:

    • Patterns or conventions discovered
    • Commands needed but not documented
    • Architectural insights
    • Common pitfalls encountered
  2. Determine where each learning belongs (lowest common ancestor):

    • Root AGENTS.md for repo-wide patterns
    • Package-level AGENTS.md for package-specific patterns
    • docs/*.md for detailed explanations
  3. Check if the target AGENTS.md already has related content:

    • If multiple related items exist, consider extracting to a docs/ page
    • If adding would make the file too long (>60 lines for root), extract to docs/
  4. Apply changes following the writing style in the guidelines

  5. List what was updated and why

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. 2d ago First seen · 30 lines · 31 tokens per session scan A 1c87170d5130

Subscribe to this mod's changes

update-docs is a skill published in the GitHub repository saffron-health/opencode-gui (57 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 234 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to update-docs, differing in 2 lines, and is treated as a copy.