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.
git 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/guard)<a href="https://agentmods.dev/commands/raccioly/docguard/guard"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/guard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/raccioly/docguard/guard"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/guard.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00012 | $0.00753 |
| Opus 5.5 | $0.00005 | $0.00301 |
| Sonnet 5.5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
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 today.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DocGuard Guard
Validate your project against its canonical documentation. Runs every enabled validator; docguard --help and the guard output report what ran.
Running DocGuard
Run docguard from PATH when it is installed. Otherwise run
npx --yes [email protected], the release these instructions ship with, in its
place. Every docguard … command below means one of the two.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Execution
- Run DocGuard guard validation:
docguard guard --format json $ARGUMENTS
-
Parse each validator's result and build a severity-ranked findings table. Status glyphs: ✅ pass, ⚠️ warning, ❌ fail, ➖ N/A (nothing to validate — NOT a pass; the dimension was not assessed).
-
Triage by severity:
- CRITICAL: Structure, Security, Test-Spec, Evidence contradiction/manifest failures → fix immediately
- HIGH: Doc Sections, Drift-Comments, Changelog, Traceability, API-Surface → fix before commit
- MEDIUM: Freshness, Docs-Coverage, Doc-Quality, Metrics → fix this sprint
- LOW: TODO-Tracking, Schema-Sync, Spec-Kit, Metadata → fix when convenient
-
For each failing check, provide an exact fix — specific file, section, and content.
-
Re-run guard after fixes. Iterate until all checks pass (max 3 iterations).
Validators
| Validator | What It Checks |
|---|---|
| Structure | Required CDD files exist |
| Doc Sections | Canonical docs have required sections |
| Docs-Sync | External doc references are valid |
| Drift-Comments | // DRIFT: comments have DRIFT-LOG entries |
| Changelog | CHANGELOG.md is maintained |
| Test-Spec | TEST-SPEC.md matches actual test files |
| Environment | Environment docs and .env.example exist |
| Security | No hardcoded secrets, .gitignore configured |
| Architecture | Layer boundaries and diagrams present |
| Freshness | Docs updated after recent code changes |
| Traceability | Canonical docs linked to source code |
| Docs-Diff | Entity/route/field drift between code and docs |
| API-Surface | API-REFERENCE.md endpoints match the real API surface (OpenAPI spec / routes) |
| Metadata-Sync | Metadata headers are consistent |
| Docs-Coverage | All config files documented |
| Doc-Quality | Readability, IEEE 830 compliance |
| TODO-Tracking | TODOs are tracked |
| Schema-Sync | Schema documentation matches code |
| Spec-Kit | Spec quality (FR-IDs, sections) |
| Evidence | Exact declared statements match current local sources or saved compatibility reports |
| Metrics-Consistency | Internal counts are accurate |
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.
- today Changed 2d672b4b4f7b
- 3d ago Changed b9c720583f43
- 5d ago Changed 6e53ce87e06d
- 6d ago Changed 6349c02ce8fa
- 15d ago Changed · +6 lines 793bf3ded87e
- 17d ago Changed 44ceaa27e31a
- 1mo ago Changed · +1 lines d486368bb9cf
- 1mo ago First seen · 75 lines · 12 tokens per session scan A 1a8a3fc7c8e3
guard is a command published in the GitHub repository raccioly/docguard (32 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 753 once invoked, about $0.0000 per session on Opus 5.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
dev-docs-update
Update dev documentation before context compaction.
dev-docs
Create a comprehensive strategic plan with structured task breakdown.
explain
Explain code or concepts clearly with practical examples and analogies.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.