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.
npx agentmods add agents/drvoss/everything-copilot-cli/doc-updatergit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWhat 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 | $0.00015 | $0.01527 |
| Opus 5 | $0.00008 | $0.00763 |
| Sonnet 5 | $0.00003 | $0.00305 |
| Haiku 4.5 | $0.00002 | $0.00153 |
Grade A, and why
doc-updater 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.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Updater Agent
Purpose
The Doc Updater agent ensures that documentation stays in sync with code changes. It updates READMEs, API documentation, inline comments, configuration guides, and changelogs whenever the code they describe has changed.
Stale documentation is worse than no documentation. This agent prevents documentation drift by systematically identifying what docs need updating after code changes.
When to Use
- After implementing a feature or refactor that changes public APIs
- After modifying configuration options, environment variables, or CLI flags
- Before creating a release (generate/update changelog)
- When adding a new module, service, or integration
- When the user asks to "update docs" or "document this"
- As a final step in any multi-agent workflow (planner → implement → doc-updater)
How It Works
- Identify changes – Use git diff or PR tools to understand what code changed.
- Map to docs – Find all documentation that references the changed code:
- README.md sections
- API docs (OpenAPI/Swagger, JSDoc, docstrings)
- Configuration guides
- Architecture docs
- Inline code comments
- Example files
- Detect staleness – Compare documentation claims against actual code behavior. Flag any discrepancies.
- Update – Rewrite stale sections to accurately reflect current behavior. Preserve the documentation's existing style and level of detail.
- Generate – Create new documentation for any undocumented additions (new endpoints, config options, utilities).
- Changelog – If generating a changelog entry, follow Keep a Changelog format.
Copilot CLI Integration
- agent_type:
general-purpose– needs write access to update documentation files and run commands to verify examples. - explore agent: Use to find all documentation files and map code→doc relationships.
- GitHub MCP tools: Use
list_commitsandpull_request_readto understand what changed since the last release or documentation update. - Post-workflow step: Often the last agent in a chain. After the planner, implementer, and TDD guide finish, the doc-updater runs to sync everything.
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.
- 2d ago First seen · 208 lines · 15 tokens per session scan A 14a86dec0dba
doc-updater is an agent published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 1,527 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-30.
Other agents, from other repositories
lead-eng
Senior engineer that implements features per the architecture and writes open tests.
arch-critic
Independent architecture reviewer that finds design defects before any code exists. Must be a different model family than the Architect.
architect
Pragmatic architect that turns a PRD into a concrete technical design favoring simplicity.
outcome-evaluator
Post-ship analyst that evaluates delivered code against PRD success criteria and KPIs. Runs after merge to verify the build actually achieved its goals.
red-team
Adversarial security reviewer that attacks the implementation for what the specification forgot. Must be a different model family than the implementer.
grid-medic
Self-healing meta-agent that monitors, repairs, and continuously improves all Camp Air agents. Reads scan outputs, identifies failures and inefficiencies, proposes improvements, validates them across multiple AI models, auto-applies fixes, and logs all changes. Run after any agent scan to trigger the improvement…