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/init)<a href="https://agentmods.dev/commands/raccioly/docguard/init"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/init/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/init"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/init.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.00009 | $0.00329 |
| Opus 5.5 | $0.00004 | $0.00132 |
| Sonnet 5.5 | $0.00002 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
init 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.
What it actually says
DocGuard Init
Initialize CDD in your project. Creates the docs-canonical/ directory, required files (CHANGELOG.md, DRIFT-LOG.md, AGENTS.md), and optionally sets a compliance profile.
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
Steps
- Run DocGuard init on the current project:
docguard init $ARGUMENTS
-
Choose a compliance profile:
- starter — Minimal CDD (architecture + changelog only)
- standard — Full CDD (all 5 canonical docs)
- enterprise — Strict CDD (all docs, all validators, freshness enforced)
-
After init, run
speckit.docguard.generateto populate the canonical docs with real data from your codebase.
Flags
--profile <name>— Set compliance profile (starter, standard, enterprise)--dir <path>— Run on a different directory
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 58d692583f6d
- 3d ago Changed f47858177f03
- 5d ago Changed e99d79af38f8
- 6d ago Changed e11e2b4a6de8
- 15d ago Changed · +6 lines 826bb7022835
- 1mo ago First seen · 39 lines · 9 tokens per session scan A a4f7a07da264
init is a command published in the GitHub repository raccioly/docguard (32 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 329 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.