docs-maintain

A documentation checker that revalidates claims against supporting evidence, either incrementally or across the whole documentation set. It first checks which runtime capabilities are available and states when checks are reduced.

In plain words
What is it for?
Use it to review documentation after changes, validate selected sections, or run a complete evidence check.
Why use it?
It helps catch documentation that is no longer supported by evidence and makes limitations in the checking process explicit.

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/simon-hwang/gg-plugins/docs-maintain
Clone the repo
git clone --depth 1 https://github.com/Simon-Hwang/gg-plugins
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 217 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00020 $0.00217
Opus 5 $0.00010 $0.00109
Sonnet 5 $0.00004 $0.00043
Haiku 4.5 $0.00002 $0.00022

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

Security

Grade A, and why

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

plugins/gg/commands/docs-maintain.md · 24 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 24 lines · 20 tokens per session scan A aa7297a4ac22

Subscribe to this mod's changes

docs-maintain is a command published in the GitHub repository Simon-Hwang/gg-plugins (2 stars, last pushed 1mo ago), with no licence file. It adds 20 tokens to every session and 217 once invoked, about $0.0001 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.