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.guardgit 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.guard)<a href="https://agentmods.dev/commands/raccioly/docguard/docguard.guard"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/docguard.guard.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.00013 | $0.00733 |
| Opus 5 | $0.00006 | $0.00367 |
| Sonnet 5 | $0.00003 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
docguard.guard 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/docguard.guard — Validate CDD Compliance
You are an AI agent enforcing Canonical-Driven Development (CDD) compliance using DocGuard.
Step 1: Run Guard (machine-readable)
npx docguard-cli guard --format json
Read the JSON contract — do not parse prose:
| Field | Meaning |
|---|---|
status |
PASS / WARN / FAIL (severity-aware; matches the exit code: 0/2/1) |
findings[] |
Structured issues: {code, severity, confidence, message, location, suggestion} |
nextStep |
The single suggested follow-up command (null on PASS) |
reportable[] |
Low-confidence findings (possible false positives) — verify before acting |
coverage |
Markdown tier map: canonical / tracked / ignored / unclassified[] |
semanticClaims.count |
Documented counts/limits/enums NOT yet verified against code |
validators[] |
Per-validator results, including na (nothing to validate ≠ pass) |
Step 2: Understand each finding before fixing
- Every finding carries a stable code (e.g.
STR001,ENV003,XRF002). Runnpx docguard-cli explain <CODE>for its contract, cause, and remediation. confidence: "low"means the scanner itself is unsure — verify against the code before changing anything, and report real false positives withnpx docguard-cli feedback.- A finding's
suggestionmay include a ready-to-runcommandor an inlinepragma. Prefer those over inventing your own fix.
Step 3: Fix, suppress, or escalate
- Mechanical issues first:
npx docguard-cli fix --writeapplies safe, provenance-checked fixes (broken anchors, stale counts/versions). Never hand-edit what the tool can fix deterministically. - Prose/content issues: follow the
/docguard.fixworkflow (research → write real content). - Genuine false positives: suppress at the finding site with the code —
// docguard:ignore <CODE>on (or above) the flagged line — or mark a whole validator not-applicable in a doc:<!-- docguard:validator <key> n/a — reason -->. Always include the reason. Never suppress to silence a real issue. - If
semanticClaims.count > 0, offer to runnpx docguard-cli verify --semanticand check each extracted claim against the code — a green guard asserts structure, not the truth of documented numbers.
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 · 68 lines · 13 tokens per session scan A 5e58038377de
docguard.guard is a command published in the GitHub repository raccioly/docguard (27 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 733 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.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
archive
Manually archive completed increments and sync living docs - NEVER auto-archives, explicit user action only.