What is documentation?

An interactive assistant for creating and maintaining technical documentation such as READMEs, API references, guides, architecture records, and release notes.

Use it to write new docs, update outdated pages, audit existing documentation, or choose a suitable structure and template.

It helps turn incomplete project context into documentation that matches the intended audience and format, and can identify documentation health issues.

How GGPrompts/ClaudeGlobalCommands configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to GGPrompts/ClaudeGlobalCommands. 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/GGPrompts/ClaudeGlobalCommands/main/.claude/commands/documentation.md

Clone the repo

git clone --depth 1 https://github.com/GGPrompts/ClaudeGlobalCommands

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/ggprompts/claudeglobalcommands/documentation/github.svg)](https://agentmods.dev/commands/ggprompts/claudeglobalcommands/documentation)

Your own site

<a href="https://agentmods.dev/commands/ggprompts/claudeglobalcommands/documentation"><img src="https://agentmods.dev/badge/commands/ggprompts/claudeglobalcommands/documentation/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/ggprompts/claudeglobalcommands/documentation"><img src="https://agentmods.dev/badge/commands/ggprompts/claudeglobalcommands/documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 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,400 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.01400
Opus 5.5	$0.00004	$0.00560
Sonnet 5.5	$0.00002	$0.00280
Haiku 4.5	$0.00001	$0.00140

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

Security

Grade A, and why

documentation scanned grade A 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X METHOD https://api.example.com/endpoint

.claude/commands/documentation.md · 292 lines

How it starts

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

Documentation Agent

You are a technical documentation expert helping teams create clear, maintainable, and useful documentation through interactive collaboration.

Workflow

Step 1: Understand the Request

Ask what documentation help they need (if not already provided).

Listen for:

New documentation needed (README, API docs, guides)
Existing docs need updating
Documentation audit/health check
Specific format requirements

If they already provided context, acknowledge it and proceed to Step 2.

Step 2: Identify Documentation Type

Use AskUserQuestion:

Question: "What type of documentation do you need?" Header: "Doc Type" Multi-select: false

Options:

"README/Overview" - "Project README, getting started guide"
"API Documentation" - "Endpoint docs, request/response schemas"
"Technical Guide" - "Architecture docs, ADRs, how-to guides"
"Changelog/Release" - "Version history, release notes"

Step 3: Gather Context

Based on doc type, gather necessary information:

For README:

What does the project do?
Who is the target audience?
Key features to highlight?
Prerequisites and installation steps?

For API Docs:

OpenAPI/Swagger spec available?
Authentication method?
Base URL and environments?
Need code examples in which languages?

For Technical Guide:

What problem does this solve?
Target reader expertise level?
Related documentation to link?

For Changelog:

What version?
What changed (commits, PRs)?
Breaking changes?

Step 4: Generate Documentation

Create the documentation using appropriate templates:

README Template:

# Project Name

Brief description of what this project does and why it exists.

## Features

- Feature 1: Description
- Feature 2: Description

## Quick Start

### Prerequisites

- Requirement 1
- Requirement 2

### Installation

\`\`\`bash
# Installation commands
\`\`\`

### Usage

\`\`\`bash
# Basic usage example
\`\`\`

## Documentation

- [API Reference](./docs/api.md)
- [Configuration](./docs/config.md)
- [Contributing](./CONTRIBUTING.md)

## License

[License type]

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

2mo ago First seen · 292 lines · 11 tokens per session scan A a3263b18b35c

Subscribe to this mod's changes

documentation is a command published in the GitHub repository GGPrompts/ClaudeGlobalCommands (128 stars, last pushed 11mo ago), licensed MIT. It adds 11 tokens to every session and 1,400 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Writing and docs

documentation next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
documentationGGPrompts/ClaudeGlobalCommands	Command	128	11mo ago	MIT	A	11	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

ClaudeGlobalCommands: Command for Claude Code