agentmods.dev

agentcmd: Command for Claude Code

.claude/commands/refresh-docs.md

refresh-docs is a command for Claude Code from jnarowski/agentcmd. It costs 8 tokens per session (2,628 once invoked), scanned A, original, MIT.

A command that regenerates selected parts of a project’s documentation from the current code. It updates generated sections while keeping manually written content intact.

In plain words
What is it for?
Use it to refresh API, CLI, configuration, examples, workflow, or all supported documentation sections.
Why use it?
It reduces the chance that documentation falls behind the software it describes.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; positional $N argument; mentions Claude Code.

This is jnarowski/agentcmd's own configuration. It tells Claude Code how to work on agentcmd itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentcmd configures →

not rated 18repo 10mo ago A scan 8 tokens original MIT
View source ↗ jnarowski/agentcmd agentcmd.dev
Reuse

Borrowing it

Nothing to install: this file belongs to jnarowski/agentcmd. 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/jnarowski/agentcmd/main/.claude/commands/refresh-docs.md
Clone the repo
git clone --depth 1 https://github.com/jnarowski/agentcmd

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/jnarowski/agentcmd/refresh-docs/github.svg)](https://agentmods.dev/commands/jnarowski/agentcmd/refresh-docs)
Your own site
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/refresh-docs"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/refresh-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 refresh-docs

Your own site · 80×15
<a href="https://agentmods.dev/commands/jnarowski/agentcmd/refresh-docs"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/refresh-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,628 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.02628
Opus 5.5 $0.00003 $0.01051
Sonnet 5.5 $0.00002 $0.00526
Haiku 4.5 $0.00001 $0.00263

Measured 2mo ago against content hash ba852b7f205c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

refresh-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 2mo 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/commands/refresh-docs.md · 371 lines

How it starts

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

Refresh Documentation

Regenerate AgentCmd documentation by extracting current state from codebase sources of truth. Updates AUTO-GENERATED sections while preserving hand-crafted content.

Variables

  • $section: $1 (optional) - Specific section to refresh or 'all' (default: all)
  • Valid sections: step-types, sdk-api, slash-commands, cli, config, examples, all

Documentation Decisions

These decisions guide all documentation generation:

  • Audience: Intermediate (familiar with AI CLI tools like Claude Code, Cursor)
  • Format: Section-appropriate
    • Concepts/philosophy pages: Mermaid diagrams, visual explanations
    • Reference/API pages: Code-heavy with minimal prose
  • Examples: Tiered complexity
    • Getting Started: Ultra-simple (5-10 lines, single concept)
    • Step Types Reference: Focused snippets (isolated examples)
    • Examples & Recipes: Real workflows (from .agent/workflows/definitions/example-*.ts)
    • Advanced Topics: Production patterns with full context
  • Tone: Technical & concise but fun
  • Structure: Follow Fumadocs conventions (meta.json, frontmatter)
  • Update Strategy: Generated docs serve as templates for future runs

Workflow

  1. Extract context from 6 sources (load current codebase state)
  2. Read existing docs (use as templates)
  3. Generate updated content (surgical updates to AUTO-GENERATED sections)
  4. Validate comprehensively (links, syntax, signatures)
  5. Write updated files (no auto-commit)
  6. Report (changed files, warnings)

Sources of Truth

Load context from these 6 sources to inform documentation generation:

1. TypeScript Types

Source: packages/agentcmd-workflows/src/types/steps.ts Generates: Step Types Reference (all 8 step configs with signatures, timeouts) Extraction: Read file, extract interface definitions for:

  • AgentStepConfig, AiStepConfig, CliStepConfig, GitStepConfig
  • ArtifactStepConfig, AnnotationStepConfig, PhaseOptions
  • Note timeout constants in comments

Read the full file on GitHub · 371 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. 2mo ago First seen · 371 lines · 8 tokens per session scan A ba852b7f205c

Subscribe to this mod's changes

refresh-docs is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 2,628 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-09-01.

Writing and docs
Related

refresh-docs compared with commands from other repositories

refresh-docs next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
refresh-docsjnarowski/agentcmdCommand1810mo agoMITA8Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code