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/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.00011 | $0.00377 |
| Opus 5 | $0.00005 | $0.00188 |
| Sonnet 5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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 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 Score
Calculate your project's Canonical-Driven Development maturity score (0-100) across 8 weighted categories.
User Input
$ARGUMENTS
Steps
- Run DocGuard score on the current project:
npx --yes docguard-cli@latest 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.
- 2d ago First seen · 54 lines · 11 tokens per session scan A 454cf81af070
score is a command published in the GitHub repository raccioly/docguard (27 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 377 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
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.