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.reviewgit clone --depth 1 https://github.com/raccioly/docguardWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/raccioly/docguard/docguard.review)<a href="https://agentmods.dev/commands/raccioly/docguard/docguard.review"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/docguard.review.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00012 | $0.00582 |
| Opus 5 | $0.00006 | $0.00291 |
| Sonnet 5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
docguard.review 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 5d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/docguard.review — Review Documentation vs Code
You are an AI agent reviewing documentation quality and detecting drift between docs and code.
Step 1: Run Diagnostics
npx docguard-cli diagnose
npx docguard-cli diff
npx docguard-cli score
Read all output. Identify where documentation no longer matches the codebase.
Findings carry stable codes — npx docguard-cli explain <CODE> when unclear.
Step 2: Verify Documented Claims Against Code
npx docguard-cli verify --semantic
This extracts every checkable claim in the canonical docs — counts, limits, rate numbers, retention windows, status enums — as a task list with the nearest cited code path. You perform each verification: read the cited code, compare the value, and report every mismatch with both values. This is the highest-value review step; deterministic validators cannot judge these.
Step 3: Semantic Analysis (Beyond CLI)
For each canonical doc, verify alignment with actual code:
| Analysis | What to Check |
|---|---|
| Architecture ↔ Code | Components in ARCHITECTURE.md exist as real modules |
| Data Model ↔ Code | Schemas in DATA-MODEL.md match actual implementations |
| Security Claims | Auth mechanisms in SECURITY.md match actual code |
| Test Coverage | Critical flows in TEST-SPEC.md have actual test files |
| Terminology | Same concepts named consistently across all docs |
Step 4: Update Stale Docs
For each stale or drifted document:
- Decide which side is wrong first. Canonical docs are the spec — if the
code regressed from a documented decision, flag the code (or record a
// DRIFT: reason+ DRIFT-LOG.md entry); don't rewrite the doc to match a regression. - Sections inside
<!-- docguard:section ... source=code -->markers are regenerated — runnpx docguard-cli sync --writeinstead of editing by hand. - For hand-maintained sections: read the relevant source, update the specific
section, refresh
docguard:last-reviewedto today. - Add entry to CHANGELOG.md under [Unreleased].
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.
- 5d ago First seen · 72 lines · 12 tokens per session scan A b27c99a4a02f
docguard.review is a command published in the GitHub repository raccioly/docguard (27 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 582 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
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
/add-claude-rule
Appends the rule from $ARGUMENTS to CLAUDE.md.
implement-regression-tests
Implement regression tests marked with it.skip.
read-issue
Fetch and read a GitHub issue using gh command.
release-note-csoar
Automates the creation of Cloud SOAR (Automation Service) release notes for platform updates, integration changes, and bug fixes.