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/score)<a href="https://agentmods.dev/commands/raccioly/docguard/score"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/score/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/score"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/score.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.00011 | $0.00431 |
| Opus 5.5 | $0.00004 | $0.00172 |
| Sonnet 5.5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
score 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 Score
Calculate your project's Canonical-Driven Development maturity score (0-100) across 8 weighted categories.
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 score on the current project:
docguard score $ARGUMENTS
-
Review the breakdown:
- Structure (25%) — required files present
- Doc Quality (20%) — docs have required sections
- Testing (15%) — test spec alignment
- Security (10%) — no hardcoded secrets
- Environment (10%) — env docs configured
- Drift (10%) — drift tracking discipline
- Changelog (5%) — changelog maintenance
- Architecture (5%) — layer boundary compliance
-
For per-signal quality labels, add
--signals.
Grading
| Score | Grade | Status |
|---|---|---|
| 90-100 | A | Strong CDD compliance |
| 75-89 | B | Good, some gaps |
| 50-74 | C | Needs work |
| < 50 | D | Significant gaps |
Flags
--signals— Show multi-signal CJE composite breakdown with quality labels--tax— Show estimated maintenance effort--format json— Output as JSON
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 9d7ef5d10a5e
- 3d ago Changed 9891bcc11620
- 5d ago Changed 3e9a8bf43739
- 6d ago Changed a2c5f348046c
- 15d ago Changed · +6 lines bf0bf72394ce
- 1mo ago First seen · 54 lines · 11 tokens per session scan A 454cf81af070
score is a command published in the GitHub repository raccioly/docguard (32 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 431 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.