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 commands/raccioly/docguard/docguard.updategit clone --depth 1 https://github.com/raccioly/docguardWhat 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.00012 | $0.00483 |
| Opus 5 | $0.00006 | $0.00242 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
docguard.update 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.
What it actually says
/docguard.update — Update Docs After Code Changes
You are an AI agent that updates documentation to reflect recent code changes.
Step 1: Identify What Changed
npx docguard-cli diff --since HEAD~5
git log --oneline -10
diff --since maps the changed files directly to the canonical docs they
affect — read its output first; the git log supplies the "why".
Step 2: Check Which Docs Are Affected
For each changed file, determine which canonical doc it affects:
| Code Change | Update This Doc |
|---|---|
| New API endpoint or route | ARCHITECTURE.md (component map) |
| Database schema change | DATA-MODEL.md (entities, fields) |
| New env variable | ENVIRONMENT.md (env var table) |
| Auth or permission change | SECURITY.md (auth/RBAC section) |
| New test or test config | TEST-SPEC.md (test categories) |
| New dependency added | ARCHITECTURE.md (tech stack) |
| Major refactoring | ARCHITECTURE.md (layer boundaries, data flow) |
Step 3: Update Each Affected Doc
Mechanical layers first — they update marked sections and counts without AI judgment:
npx docguard-cli sync --write
npx docguard-cli fix --write
Then, for each remaining affected document:
- Read the current document
- Read the relevant source code changes
- Update the specific section that changed (never hand-edit inside
<!-- docguard:section ... source=code -->markers — sync owns those) - Update the
docguard:last-revieweddate to today - Add entry to CHANGELOG.md under [Unreleased]
Step 4: Verify
npx docguard-cli guard
npx docguard-cli score
All checks should pass. Report the changes made and the final score.
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.
- 3d ago First seen · 66 lines · 12 tokens per session scan A 3d05e6bea30f
docguard.update is a command published in the GitHub repository raccioly/docguard (27 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 483 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 commands, from other repositories
implement-regression-tests
Implement regression tests marked with it.skip.
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
github-status
Check GitHub sync status for SpecWeave increment. Shows issue number, sync state, progress, last update, and any sync issues. Useful for troubleshooting and monitoring.
save
Command "save" from anton-abyzov/specweave, covering save changes across repositories, usage, interactive (prompts for commit message), dry run (show what would happen, don't execute) and save specific repos only (umbrella mode).
github-push
Push local progress to GitHub Issues (like git push). Updates issue with task completion checklist.