Borrowing it
Nothing to install: this file belongs to raccioly/docguard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/raccioly/docguard/main/.agent/skills/docguard-score/SKILL.mdgit 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/skills/raccioly/docguard/docguard-score)<a href="https://agentmods.dev/skills/raccioly/docguard/docguard-score"><img src="https://agentmods.dev/badge/skills/raccioly/docguard/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/skills/raccioly/docguard/docguard-score"><img src="https://agentmods.dev/badge/skills/raccioly/docguard/docguard-score.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 6 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 35 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 36 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00039 | $0.02095 |
| Opus 5.5 | $0.00016 | $0.00838 |
| Sonnet 5.5 | $0.00008 | $0.00419 |
| Haiku 4.5 | $0.00004 | $0.00210 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DocGuard Score Skill
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
You MUST consider the user input before proceeding (if not empty).
Goal
Run DocGuard's CDD maturity scoring engine, analyze the category breakdown, identify highest-ROI improvements, and produce an actionable improvement roadmap showing projected score gains per fix.
Execution Flow
Step 1: Run Scoring Engine
Execute both tools for comprehensive data:
docguard score 2>&1
docguard guard 2>&1
If in DocGuard dev environment:
node cli/docguard.mjs score 2>&1
node cli/docguard.mjs guard 2>&1
Step 2: Parse Score Breakdown
Extract the category-level scores:
| Category | Score | Weight | Points | Potential Gain |
|---|---|---|---|---|
| Structure | X% | ×25 | N | [25 - N] |
| Doc Quality | X% | ×20 | N | [20 - N] |
| Testing | X% | ×15 | N | [15 - N] |
| Security | X% | ×10 | N | [10 - N] |
| Environment | X% | ×10 | N | [10 - N] |
| Drift | X% | ×10 | N | [10 - N] |
| Changelog | X% | ×5 | N | [5 - N] |
| Architecture | X% | ×5 | N | [5 - N] |
Calculate Potential Gain for each category = (weight - current points).
Step 3: Grade Classification
| Grade | Score | Description |
|---|---|---|
| A+ | 95-100 | Exemplary — production-grade documentation, CDD fully adopted |
| A | 85-94 | Strong — minor improvements possible, CI-gate ready |
| B | 70-84 | Good — documentation covers essentials, some gaps exist |
| C | 50-69 | Fair — significant documentation debt, multiple gaps |
| D | 30-49 | Poor — major structural gaps, limited doc coverage |
| F | 0-29 | Critical — documentation infrastructure missing |
Step 4: ROI-Based Improvement Roadmap
Sort categories by Potential Gain / Effort ratio:
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.
- 6d ago Changed 0af6f8bdf69b
- 9d ago Changed 79161a91b215
- 11d ago Changed 276fed6cc3dd
- 12d ago Changed c486c8c09243
- 21d ago Changed · +6 lines 37585ef85fd3
- 22d ago Changed · +8 lines b878d6ee8f97
- 1mo ago Changed · +10 lines 04d9f8fd7b76
- 1mo ago Changed d4a716e37d75
- 1mo ago Changed fb34ae6a0897
- 1mo ago First seen · 181 lines · 39 tokens per session scan A 25d5ca47d157
docguard-score is a skill published in the GitHub repository raccioly/docguard (32 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 2,095 once invoked, about $0.0002 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 skills, from other repositories
do
Work a SpecWeave increment task by task - claim, implement inside its Files, test, commit, done with evidence - alone, unattended or in lanes, then close. Use for "implement", "continue", "auto".
handoff
Hand work to another tool, account or machine and pick it up there, in two words. Use when the user says "hand off", "hand off all", "out of tokens", "switching accounts", "pick up" or "continue".
sw-do
Work a SpecWeave increment task by task - claim, implement inside its Files, test, commit, done with evidence - alone, unattended or in lanes, then close. Use for "implement", "continue", "auto".
sw-handoff
Hand work to another tool, account or machine and pick it up there, in two words. Use when the user says "hand off", "hand off all", "out of tokens", "switching accounts", "pick up" or "continue".
increment
Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach and Tasks - before writing code. Use for "plan a feature", "new increment", "let's build X".
sw-increment
Plan work as a SpecWeave increment - one spec.md with Problem, Scope, numbered ACs, Approach and Tasks - before writing code. Use for "plan a feature", "new increment", "let's build X".