agentmods.dev

release-docs

release-docs is a skill for Claude Code from ApurvBazari/claude-plugins. It costs 132 tokens per session (3,812 once invoked), scanned C, original, MIT.

A release-time documentation workflow that updates site pages, README files, project guidance, and cross-references to match the code and changes shipped. It detects required edits, applies mechanical fixes, and checks the results.

In plain words
What is it for?
Use it to synchronize documentation after a release, record which obligations were covered, and produce checks and a report for unresolved items.
Why use it?
Documentation can become inaccurate when a release changes code or structure. This workflow helps find the affected pages and verify that their claims match the source.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions CLAUDE.md.

not rated 1repo +1 changed 7d ago C scan 132 tokens original MIT

Good fit Use it to synchronize documentation after a release, record which obligations were covered, and produce checks and a report for unresolved items.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/apurvbazari/claude-plugins/release-docs
View source ↗ ApurvBazari/claude-plugins apurvbazari.github.io
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.

Any agent
npx skills add ApurvBazari/claude-plugins --skill release-docs
Clone the repo
git clone --depth 1 https://github.com/ApurvBazari/claude-plugins

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 release-docs

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/apurvbazari/claude-plugins/release-docs"><img src="https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/release-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 132 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,812 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00132 $0.03812
Opus 5.5 $0.00053 $0.01525
Sonnet 5.5 $0.00026 $0.00762
Haiku 4.5 $0.00013 $0.00381

Measured 7d ago against content hash 3da5f3c19282, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

release-docs scanned grade C with 1 finding 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 7d ago.

The scan reads SKILL.md. This mod also ships 23 executable files (scripts/cred_scan.py, scripts/docs-detect.sh, scripts/docs-lib/__main__.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .release-docs/run && mkdir -p .release-docs/run
.claude/skills/release-docs/SKILL.md · 148 lines

How it starts

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

Release Docs — Sync the Docs With What a Release Ships

You are running the release docs sync. A script has already decided what must change (the obligations). Your job has three parts: make those changes truthfully from the sources, declare coverage in the ledger, and prove the result with the checks. Read references/obligations.md (what each obligation means and how to resolve it) and references/page-style.md (rules for every page edit) before editing anything.

Arguments: mode=local (the default) or mode=ci. In mode=ci, nobody will answer a question, so never ask one. Anything that needs a person goes into the report.

Paths used below:

  • scripts: .claude/skills/release-docs/scripts/docs-detect.sh, .claude/skills/release-docs/scripts/post-checks.sh, .claude/skills/release-docs/scripts/render-check.sh and .claude/skills/release-docs/scripts/og-regen.sh
  • surfaces: .github/docs-surfaces.json (at the repo root, not under this skill)
  • ledger: .github/docs-ledger.json
  • run directory: .release-docs/run/ (gitignored). It holds before.snap, obligations.before.json, verifier.json, post-checks.md, pr-body.md and shots/.

Guard

  • .claude-plugin/marketplace.json must exist in the working directory. If it doesn't, you're not at the claude-plugins root: stop.
  • Tracked files must be clean (git diff --quiet HEAD). If they aren't, stop and say which files are dirty. Untracked files belong to the owner: never touch them.
  • mode=local: if the current branch is main or develop, run git switch -c docs/release-sync-<YYYYMMDD> first. Never commit on main or develop.
  • mode=ci: the workflow has already created the branch and written the snapshot to .release-docs/run/before.snap. Never create or switch branches, commit, or push. Never run post-checks.sh --snapshot: the workflow owns the snapshot, and --snapshot refuses to overwrite an existing file.

Step 0: Snapshot

mode=local only (CI has already done this). Start from an empty run directory, so no file from an earlier run is read as this run's:

Read the full file on GitHub · 148 lines

Files

What ships with it

25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 7d ago Changed 3da5f3c19282
  2. 10d ago Changed · +2 lines a1d89118bb41
  3. 15d ago First seen · 146 lines · 132 tokens per session scan C 722f88929816

Subscribe to this mod's changes

release-docs is a skill published in the GitHub repository ApurvBazari/claude-plugins (1 stars, last pushed yesterday), licensed MIT. It adds 132 tokens to every session and 3,812 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.

Claude CodeGit and workflowReleasesWriting and docsagentic-workflowsai-driven-developmentdeveloper-toolsmacosnotifications
Related

Other skills, from other repositories

release-sidecar

Release new versions of sidecar. Covers version tagging with semver, td dependency updates, go.mod validation, CHANGELOG updates, GoReleaser automation, Homebrew tap updates, and verification steps. Use when preparing or executing a release.

marcus/sidecar · 53 tokens

release

Prepare, verify, and publish Sutando engine releases. Use when asked to prepare a release proposal, determine a version bump, audit release documentation, validate release gates, create a release PR, tag a confirmed release, or publish GitHub release notes. Preparation is safe and non-publishing; tagging and…

sonichi/sutando · 68 tokens

release

Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.

arcee-ai/nac · 53 tokens

starcat-update-changelog

Update Starcat changelog documents in supports/starcat-pro/ by reading ALL git commits from the main Starcat project and generating categorized release notes in both English and Chinese. Use this skill whenever the user wants to update changelog, release notes, update records, or sync the changelog with recent…

starcat-app/Starcat · 98 tokens

03-release-tag

Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.

ai-driven-dev/framework · 55 tokens

publish-plugins

(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests.

vinta/hal-9000 · 26 tokens