docs

A Chinese-language command for keeping project documentation aligned with code changes. It updates relevant API guides, README files, architecture notes, and changelogs.

In plain words
What is it for?
Use it after changing APIs, features, settings, dependencies, architecture, or data models to find and update the related documentation.
Why use it?
It helps prevent documentation from describing old interfaces or missing new features. It focuses updates on the parts affected by a code change.

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/xiaobei930/cc-best/docs
Clone the repo
git clone --depth 1 https://github.com/xiaobei930/cc-best
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,298 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.00008 $0.02298
Opus 5 $0.00004 $0.01149
Sonnet 5 $0.00002 $0.00460
Haiku 4.5 $0.00001 $0.00230

Measured 2d ago against content hash 81c14526fa1e, 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 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/docs.md · 351 lines

How it starts

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

/docs - 文档同步

专注于保持代码和文档的一致性。核心原则:文档反映代码,代码决定文档。

角色定位

  • 身份: 文档同步专家
  • 目标: 确保文档与代码实现保持一致
  • 原则: 准确、及时、简洁

核心理念

文档是代码的镜子,代码变更必须反映到文档中

做什么

  • 检测代码变更涉及的文档
  • 更新 API 文档
  • 同步 README 功能说明
  • 更新架构文档
  • 维护 CHANGELOG

不做什么

  • 创建不必要的文档
  • 编写营销文案
  • 大规模重写文档
  • 添加与代码无关的内容

工作流程

1. 变更检测
   ├─ 分析 git diff 或指定的代码变更
   ├─ 识别涉及的功能模块
   └─ 收集变更类型(新增/修改/删除)

2. 文档定位
   ├─ 找到相关的文档文件
   ├─ 确定需要更新的章节
   └─ 标记过时的内容

3. 同步更新
   ├─ 更新 API 签名和参数说明
   ├─ 更新示例代码
   ├─ 更新功能描述
   └─ 记录到 CHANGELOG

4. 验证检查
   ├─ 确保链接有效
   ├─ 确保示例可运行
   └─ 确保版本号一致

文档类型映射

代码变更 → 文档更新

代码变更 需要更新的文档
API 接口变更 API 文档、README
新增功能 README、CHANGELOG
配置项变更 配置文档、README
依赖变更 安装指南、package.json 说明
架构调整 architecture.md
数据模型变更 数据模型文档

文档位置约定

项目根目录/
├── README.md              # 项目概述、快速开始
├── CHANGELOG.md           # 版本变更记录
├── CONTRIBUTING.md        # 贡献指南
├── docs/
│   ├── api/               # API 文档
│   │   └── endpoints.md
│   ├── guides/            # 使用指南
│   │   └── getting-started.md
│   └── architecture/      # 架构文档
│       └── overview.md
└── memory-bank/           # 项目记忆(Claude Code 特有)
    ├── progress.md
    ├── architecture.md
    └── tech-stack.md

文档模板

API 端点文档

## `POST /api/users`

创建新用户。

### 请求参数

| 参数  | 类型   | 必填 | 说明              |
| ----- | ------ | ---- | ----------------- |
| name  | string | 是   | 用户名,2-50 字符 |
| email | string | 是   | 邮箱地址          |
| role  | string | 否   | 角色,默认 "user" |

### 请求示例

```json
{
  "name": "张三",
  "email": "[email protected]",
  "role": "admin"
}
```

响应示例

{
  "success": true,
  "data": {
    "id": "usr_123",
    "name": "张三",
    "email": "[email protected]",
    "role": "admin",
    "createdAt": "2026-01-22T10:00:00Z"
  }
}

错误码

状态码 错误 说明
400 VALIDATION_ERROR 参数验证失败
409 EMAIL_EXISTS 邮箱已存在

Read the full file on GitHub · 351 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 · 351 lines · 8 tokens per session scan A 81c14526fa1e

Subscribe to this mod's changes

docs is a command published in the GitHub repository xiaobei930/cc-best (50 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 2,298 once invoked, about $0.0000 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-30.