docs

A command for making project plans and generating documentation. It can break a large software task into smaller pieces or document a component, project, or API.

In plain words
What is it for?
Use it to plan refactors, migrations, and new features; update development notes; or create component, project, and API documentation.
Why use it?
It gives you a structured way to plan complex work and keep useful development information recorded.

Command

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/drag88/claude-dev-framework/docs
Clone the repo
git clone --depth 1 https://github.com/drag88/claude-dev-framework
Per session 10 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,830 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00010 $0.02830
Opus 5 $0.00005 $0.01415
Sonnet 5 $0.00002 $0.00566
Haiku 4.5 $0.00001 $0.00283

Measured yesterday against content hash 6d3c30170e64, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs 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 yesterday.

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.

Verification: `pytest tests/test_service.py` passes; `curl localhost:8000/health` returns 200
commands/docs.md · 365 lines

How it starts

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

/cdf:docs - Strategic Planning & Documentation

Create strategic plans with task breakdown, or generate documentation at various scopes.

Default Behavior

When invoked without a subcommand, /cdf:docs defaults to strategic planning mode.

# These are equivalent:
/cdf:docs "refactor authentication system"
/cdf:docs plan "refactor authentication system"

If no arguments provided, ask the user what they want to plan or document.

Quick Start

# Strategic planning (DEFAULT) - describe what needs planning
/cdf:docs "refactor authentication system"
/cdf:docs "implement payment gateway"

# Explicit subcommands
/cdf:docs plan "migrate to microservices"    # Strategic planning
/cdf:docs update                              # Update dev docs before context limit
/cdf:docs src/api --scope component --type api  # Component docs

When to Use

Use /cdf:docs when:

  • Planning complex features with structured task breakdown (default behavior)
  • Preserving session context before context compaction (update)
  • Generating inline documentation or API references (--scope component)
  • Creating project documentation or knowledge bases (--scope project)

Don't use this command for: Project rules generation (use /cdf:rules instead).

Scopes

Component Scope (--scope component)

Generate focused documentation for specific components, functions, or APIs.

/cdf:docs [target] --scope component [--type inline|external|api|guide] [--style brief|detailed]

Behavioral Flow:

  1. Analyze: Examine target component structure and interfaces
  2. Identify: Determine documentation requirements and audience
  3. Generate: Create appropriate documentation based on type
  4. Format: Apply consistent structure and patterns
  5. Integrate: Ensure compatibility with existing documentation

Examples:

# Inline code documentation (JSDoc/docstrings)
/cdf:docs src/auth/login.js --scope component --type inline

# API reference generation
/cdf:docs src/api --scope component --type api --style detailed

# User guide for a module
/cdf:docs payment-module --scope component --type guide

Read the full file on GitHub · 365 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. yesterday First seen · 365 lines · 10 tokens per session scan A 6d3c30170e64

Subscribe to this mod's changes

docs is a command published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 2,830 once invoked, about $0.0001 per session on Opus 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-31.