docs-governance CLAUDE.md

A set of project instructions for governing documentation in a software repository. It defines where project rules, status, maps, history, decisions, and user guidance should live.

In plain words
What is it for?
Use it when maintaining the repository’s documentation structure or changing its governance files. It helps decide which document to update for rules, status, architecture decisions, history, or usage instructions.
Why use it?
It keeps documentation rules in one place and reduces conflicting or outdated instructions. It also requires a verification script to pass before changes are committed.

Instructions file

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 instructions/seekers2001/docs-governance/claude-md
Clone the repo
git clone --depth 1 https://github.com/Seekers2001/docs-governance
Per session 316 This file is loaded in full into every session.
When invoked 316 The same file — it is already loaded in full.
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.00316 $0.00316
Opus 5 $0.00158 $0.00158
Sonnet 5 $0.00063 $0.00063
Haiku 4.5 $0.00032 $0.00032

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

Security

Grade A, and why

docs-governance CLAUDE.md 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 3d 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.md · 19 lines

What it actually says

CLAUDE.md — docs-governance 插件自治理(用自己的方法论治自己)

进会话读取(分级):本文件全文 + PROJECT_STATUS.md 红线块;MAP / LOG 按需。 本插件刻意保持轻量治理——它自己的 skill 写着"别给小项目过度治理",这套四件套就是个薄示范,别往里堆。

硬规则

  • 方法论唯一源在 skills/*/SKILL.md;agent / command 只指过去,不复制方法论(防插件自己内部漂移)。总入口由 docs-governance skill 路由。
  • 改任何文件后、提交前:跑 bash scripts/verify.sh绿了才提交
  • 文件名 kebab-case;正文中文,英文仅保留 skill description 里的触发词。
  • commit message 用英文;git push 等小磊说。

路标

  • 结构 / 依赖 / 误导 → CLAUDE_MAP.md
  • 当前健康 / 待办 → PROJECT_STATUS.md
  • 改了什么 → PROJECT_LOG.md
  • 方法论本体 → skills/*/SKILL.md
  • 架构 / 数据库决策 → docs/adr/README.md
  • 给用户怎么用 → README.md / 使用说明.md
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. 3d ago First seen · 19 lines · 316 tokens per session scan A 40f51aa330e4

Subscribe to this mod's changes

docs-governance CLAUDE.md is an instructions file published in the GitHub repository Seekers2001/docs-governance (11 stars, last pushed 21d ago), licensed MIT. It adds 316 tokens to every session, about $0.0016 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens