A documentation-maintenance instruction that keeps the project README, GitHub wiki, and Claude instructions aligned with recent changes. A README is the main project guide, and a wiki is a set of linked documentation pages.

Use it after changing commands, skills, installation steps, or project behavior so the relevant documentation can be updated and committed.

It reduces the chance that installation, usage, or available-command instructions become outdated. It also keeps internal instructions separate from commands users can run.

How 1shooperman/claude-env configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to 1shooperman/claude-env. 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/1shooperman/claude-env/main/.claude/skills/update-docs/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/1shooperman/claude-env

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/1shooperman/claude-env/update-docs/github.svg)](https://agentmods.dev/skills/1shooperman/claude-env/update-docs)

Your own site

<a href="https://agentmods.dev/skills/1shooperman/claude-env/update-docs"><img src="https://agentmods.dev/badge/skills/1shooperman/claude-env/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/1shooperman/claude-env/update-docs"><img src="https://agentmods.dev/badge/skills/1shooperman/claude-env/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 425 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.

Model	Per session	Once invoked
Fable 5.1	$0.00010	$0.00425
Opus 5.5	$0.00004	$0.00170
Sonnet 5.5	$0.00002	$0.00085
Haiku 4.5	$0.00001	$0.00042

Measured 1mo ago against content hash 8fffffe1dc58, 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 · 41 lines

What it actually says

Instruction

Keep all documentation in sync after changes. Three targets:

Root README — README.md at repo root; reflects the full usage and install / upgrade instructions
GitHub wiki — markdown pages in wiki/claude-env.wiki/; committed and pushed to the wiki remote after changes
Root CLAUDE.md - baseline Claude instructions. Keep up to date with relevant bits from the current session. Prefer efficient token usage over verbosity for CLAUDE.md files.

Rules

Only list user-invocable: true skills in READMEs — do not expose internal dependency skills
Do not conflate internal references with user-invocable commands

Arguments

The user invoked this with: $ARGUMENTS

Instructions

When this skill is invoked:

Read git log --oneline -10 and git diff HEAD~1..HEAD --name-only to understand what changed
Update root README.md if the instruction list changed
Update the wiki:
- Edit wiki/claude-env.wiki/Home.md with a current overview of available commands and skills
- Create or update additional wiki pages (e.g. Hook-Permissions.md, Cache-Architecture.md) if the change warrants it
- Commit and push the wiki changes:
```
git -C wiki/claude-env.wiki add -A
git -C wiki/claude-env.wiki commit -m "docs: sync wiki after <brief summary>"
git -C wiki/claude-env.wiki push
```
Report what was updated across all three targets

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.

1mo ago First seen · 41 lines · 10 tokens per session scan A 8fffffe1dc58

Subscribe to this mod's changes

update-docs is a skill published in the GitHub repository 1shooperman/claude-env (2 stars, last pushed 26d ago), licensed MIT. It adds 10 tokens to every session and 425 once invoked, about $0.0000 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.

Claude Code Writing and docs bash install shell version-manager zsh

mbo-plan

Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…

sfc-gh-eraigosa/dotfiles · 260 tokens

pr-grooming

Use when the user wants to groom, triage, or clean up the open pull requests of a repo: "groom the PRs", "review the open PRs", "which drafts are stale", "close old draft PRs", "rebase the dependabot PRs", "are the open PRs still mergeable", "refresh that old bugfix PR", or a periodic PR review — even when they do not…

sfc-gh-eraigosa/dotfiles · 147 tokens

herdr

Use when the user mentions herdr or is working inside a herdr pane and wants to save/restore a pane layout, change herdr's theme, prefix or other preferences on this host only, start or check on an agent in another herdr pane, add, turn off or open a herdr plugin (file viewer, keybindings), or asks why the herdr…

sfc-gh-eraigosa/dotfiles · 91 tokens

issue-grooming

Use when the user wants to groom, triage, prioritize, or clean up the GitHub issue backlog of a repo: "groom the issues", "triage the backlog", "which issues are already done", "prioritize the open issues", "close stale issues", "label issues 1-5", "refactor old issues to match the repo", or a periodic backlog review…

sfc-gh-eraigosa/dotfiles · 140 tokens

wispr-flow-debug

Debug and test the Wispr Flow AutoHotkey dictation triggers (Copilot key + extra keys) from WSL by deploying macos.ahk to the Windows Desktop, reloading AutoHotkey, and reading the debug log. Use when an activation/trigger key isn't starting/stopping dictation, when the overlay clicks land wrong, or when verifying a…

sfc-gh-eraigosa/dotfiles · 87 tokens

google-docs

Integration for interacting with Google Docs and Google Workspace using the 'gws' CLI.

sfc-gh-eraigosa/dotfiles · 21 tokens

claude-env: Skill for Claude Code