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/initgit 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.00009 | $0.00275 |
| Opus 5 | $0.00005 | $0.00138 |
| Sonnet 5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 2d 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 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.
User Input
$ARGUMENTS
Steps
- Run DocGuard init on the current project:
npx --yes docguard-cli@latest 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.
- 2d ago First seen · 39 lines · 9 tokens per session scan A a4f7a07da264
init is a command published in the GitHub repository raccioly/docguard (27 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 275 once invoked, about $0.0000 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.
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.