A documentation-maintenance command for repositories that contain skills, agents, or commands. It checks changes and synchronizes them across supported agent tools.

Use it after creating, modifying, or deleting skills, agents, or commands to inventory changes and run documentation syncs.

It reduces the chance that newly created or changed resources are missing from indexes or other command-line environments.

update-docs — Command for Claude Code by afaizalam2003

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/afaizalam2003/Master-claude-skill

agentmods

npx agentmods add commands/afaizalam2003/master-claude-skill/update-docs

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/commands/afaizalam2003/master-claude-skill/update-docs/github.svg)](https://agentmods.dev/commands/afaizalam2003/master-claude-skill/update-docs)

Your own site

<a href="https://agentmods.dev/commands/afaizalam2003/master-claude-skill/update-docs"><img src="https://agentmods.dev/badge/commands/afaizalam2003/master-claude-skill/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/commands/afaizalam2003/master-claude-skill/update-docs"><img src="https://agentmods.dev/badge/commands/afaizalam2003/master-claude-skill/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,761 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 100% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00007	$0.01761
Opus 5.5	$0.00003	$0.00704
Sonnet 5.5	$0.00001	$0.00352
Haiku 4.5	$0.00001	$0.00176

Measured 1mo ago against content hash eb557a7e4d02, 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.

Origin

This is a copy

100% identical to update-docs — 0 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.

.claude/commands/update-docs.md · 229 lines

How it starts

The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.

After completing any skill creation, agent creation, or command creation in this repository, run the full post-creation sync pipeline below. Execute every step — never skip a task. If something is unclear or a step fails, ask the user for guidance before continuing.

Step 1: Inventory what changed

Scan the working tree to identify what was added, modified, or deleted:

git status --short

Classify each change:

New skill — a new folder containing SKILL.md under a domain directory
New agent — a new .md file under agents/
New command — a new .md file under commands/
Modified skill/agent/command — updated existing files
Deleted skill/agent/command — removed files

Report the inventory to the user before proceeding.

Step 2: Cross-platform CLI sync

Ensure all platforms have compatible versions of every skill, agent, and command.

2a. Codex CLI

Run the Codex sync script to regenerate symlinks and the skills index:

python3 scripts/sync-codex-skills.py --verbose

Verify the output: check .codex/skills-index.json for correct total_skills count and that new skills appear in the index.

2b. Gemini CLI

Run the Gemini sync script:

python3 scripts/sync-gemini-skills.py --verbose

Verify: check .gemini/skills-index.json for correct total count. New skills, agents, and commands should all have corresponding entries and symlinks under .gemini/skills/.

2c. OpenClaw

Verify that scripts/openclaw-install.sh will pick up the new skills. The install script uses the same directory structure, so no separate sync is needed — but confirm the new skill directories are not excluded by any filter in the script.

Report sync results (skill counts per platform) to the user.

Step 3: Claude Code plugin marketplace

3a. Domain-level plugin.json

For each domain that had changes, update the domain's .claude-plugin/plugin.json:

Update description with accurate skill/tool/reference counts
Update version if needed
Verify source paths are correct

Read the full file on GitHub · 229 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.

1mo ago First seen · 229 lines · 7 tokens per session scan A eb557a7e4d02

Subscribe to this mod's changes

update-docs is a command published in the GitHub repository afaizalam2003/Master-claude-skill (2 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 1,761 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to update-docs, differing in 0 lines, and is treated as a copy.

Building agents Claude Code Writing and docs ai-agents ai-coding-assistant ai-personas claude codex

bet

Lock a shaped Shape-Up pitch as a bet for the next cycle.

gosha70/code-copilot-team · 0 tokens

Diagnose

Run a 20-point health check across the plugin install, project config, PM/notification reachability, docs freshness, board consistency, and git state. Read-only — never changes state. Reports each check as PASS/WARN/FAIL/SKIP with an actionable fix. Target under 15 seconds end-to-end. Use before demos, after a plugin…

Evyasys-Software-Solutions/EvyaGovernance · 81 tokens

update-docs