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.scoregit 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.00020 | $0.00546 |
| Opus 5 | $0.00010 | $0.00273 |
| Sonnet 5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
docguard.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 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.
What it actually says
DocGuard Score — CDD Maturity Assessment
Calculate and display the project's Canonical-Driven Development maturity score with ROI-based improvement roadmap.
What to do
- Run the scoring engine:
npx docguard-cli score
- For JSON output (CI/CD integration):
npx docguard-cli score --format json
-
Interpret the grade:
Grade Score Meaning A+ 95-100 Exemplary — production-grade documentation A 85-94 Strong — minor improvements possible B 70-84 Good — some gaps to address C 50-69 Fair — significant documentation debt D 30-49 Poor — major gaps in documentation F 0-29 Critical — documentation infrastructure missing -
Analyze category breakdown (sorted by weight):
Category Weight What It Measures Structure 25% Required CDD files exist Doc Quality 20% Readability, sections, IEEE 830 compliance Testing 15% Test documentation coverage Security 10% Security docs, secrets handling Environment 10% Environment and setup docs Drift 10% Code deviation tracking Changelog 5% Change log maintenance Architecture 5% Architecture documentation -
Build an ROI-ranked improvement roadmap:
- Calculate
Potential Gain = weight - current pointsfor each category - Sort by
Potential Gain / Effortratio - Show: "If you fix [X], score will increase from [Y] to [Z]"
- Show the minimum set of fixes to reach the next grade level
- Calculate
-
Track progress: Compare current score against previous runs to show improvement.
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 · 62 lines · 20 tokens per session scan A c2d55097005c
docguard.score is a command published in the GitHub repository raccioly/docguard (27 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 546 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
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.
github-status
Check GitHub sync status for SpecWeave increment. Shows issue number, sync state, progress, last update, and any sync issues. Useful for troubleshooting and monitoring.
save
Command "save" from anton-abyzov/specweave, covering save changes across repositories, usage, interactive (prompts for commit message), dry run (show what would happen, don't execute) and save specific repos only (umbrella mode).
github-push
Push local progress to GitHub Issues (like git push). Updates issue with task completion checklist.