agentmods.dev

doc-refresh

A command that brings project documentation up to date after code changes, releases, or routine maintenance. It checks the changes and updates only the affected documents.

In plain words
What is it for?
Use it to refresh changelogs, README feature sections, user guides, project context files, file indexes, registry details, and other affected documentation.
Why use it?
It removes the need to search through every document after a release and helps prevent instructions from describing outdated behavior.

Command

7 3mo ago A scan 17 tokens original MIT
View the source file littlebearapps/pitchdocs
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 commands/littlebearapps/pitchdocs/doc-refresh
Clone the repo
git clone --depth 1 https://github.com/littlebearapps/pitchdocs
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 963 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00017 $0.00963
Opus 5 $0.00009 $0.00481
Sonnet 5 $0.00003 $0.00193
Haiku 4.5 $0.00002 $0.00096

Measured 2d ago against content hash 815771dcaf6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

doc-refresh 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.

commands/doc-refresh.md · 87 lines

How it starts

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

/doc-refresh

Refresh existing documentation to reflect the current state of the codebase. Analyses git history since the last release, identifies what changed, and surgically updates only the affected docs.

Behaviour

  1. Load the doc-refresh skill for the orchestration workflow
  2. Load the doc-standards rule for tone and quality
  3. If GitHub MCP tools are unavailable (GitLab/Bitbucket), gather equivalent data via glab CLI, REST API, or git history. Load platform-profiles for CI/CD equivalents.
  4. Detect the change boundary (latest tag, provided version, or range)
  5. Parse conventional commits and classify changes by type and doc impact
  6. Detect file-level changes to identify which areas of the project changed
  7. Build a refresh plan mapping changes to doc updates
  8. Execute the plan, loading additional skills as needed:
    • changelog for CHANGELOG updates
    • feature-benefits for README features
    • user-guides for affected guides
    • ContextDocs for context file drift (if installed)
    • llms-txt for file index updates
    • package-registry for registry metadata
    • docs-verify for final verification
  9. Report what was updated and the quality score

Arguments

  • No arguments: Detect latest tag, analyse changes since that tag, refresh all affected docs
  • Version (e.g., 1.7.0): Refresh docs for a specific version release
  • Range (e.g., v1.5.0..v1.7.0): Refresh docs for a range of versions (useful for catching up)
  • plan: Dry run — analyse and report what needs refreshing, without writing anything
  • changelog: Only refresh CHANGELOG.md
  • readme: Only refresh README.md features and metrics
  • guides: Only update affected user guides
  • context: Only refresh AI context files and llms.txt
  • release-notes: Only generate GitHub release body
  • full: Refresh everything regardless of what changed

Release-Please Integration

Run /doc-refresh before merging a release-please PR:

Read the full file on GitHub · 87 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. 2d ago First seen · 87 lines · 17 tokens per session scan A 815771dcaf6c

Subscribe to this mod's changes

doc-refresh is a command published in the GitHub repository littlebearapps/pitchdocs (7 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 963 once invoked, about $0.0001 per session on Opus 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.

Writing and docschangelog-generatorclaude-codeclaude-code-plugindeveloper-toolsdocumentationdocumentation-generator
Related

Other commands, from other repositories

create-skill

Create an AI skill from any source (URL, repo, PDF, video, notebook, etc.).

yusufkaraaslan/Skill_Seekers · 20 tokens

install-skill

One-command skill creation and packaging for a target platform.

yusufkaraaslan/Skill_Seekers · 10 tokens

sync-config

Sync a scraping config's URLs against the live documentation site.

yusufkaraaslan/Skill_Seekers · 11 tokens

review-renovate

Review and merge renovate PRs with automerge configuration updates.

liam-hq/liam · 11 tokens

plan-regression-tests

Plan regression tests for existing code with it.skip statements.

liam-hq/liam · 15 tokens

ado-pull

Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.

anton-abyzov/specweave · 23 tokens