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-guard/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-guard)<a href="https://agentmods.dev/skills/raccioly/docguard/docguard-guard"><img src="https://agentmods.dev/badge/skills/raccioly/docguard/docguard-guard/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-guard"><img src="https://agentmods.dev/badge/skills/raccioly/docguard/docguard-guard.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 7 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 32 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 47 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.00053 | $0.02753 |
| Opus 5.5 | $0.00021 | $0.01101 |
| Sonnet 5.5 | $0.00011 | $0.00551 |
| Haiku 4.5 | $0.00005 | $0.00275 |
Grade A, and why
docguard-guard 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DocGuard Guard 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
Execute DocGuard's full guard validator suite against the current project, parse structured results, triage findings by disposition and severity, and produce an actionable remediation plan. This skill transforms raw CLI output into an AI-digestible quality assessment.
Triage on disposition first, severity second
Every finding answers three independent questions. Reading only severity conflates them and leads to auto-fixing judgement calls.
| Field | Question | Values |
|---|---|---|
disposition |
Who decides — the tool or a human? | act, escalate |
severity / effectiveSeverity |
Does CI block? | error, warn, info |
confidence |
How sure is the detector of its observation? | high, low |
evidence.status |
Has the reviewed corpus ever measured this code? | measured, not-measured |
parserTier |
Which analyzer produced it? | js-ast, py-ast, regex-fallback, fallback-language, mixed, not-applicable |
act— DocGuard asserts a defect and names the correction. Safe to apply, including through thedocguard-fixskill.escalate— DocGuard observed a signal; the judgement belongs to the reader. Never auto-fix these. Read the source, decide which side is wrong, and say so. FRS002 is the canonical example: the commit count is exact and the finding isconfidence: high, yet it establishes only that a review is DUE, never that the document is stale.
These axes vary independently. A blocking error can be an escalate; a high-confidence finding can still need a human.
- Read
evidence.statusbefore trusting a confidence label.measuredquotes the reviewed corpus withnand a Wilson interval;not-measuredmeans the label is a maintainer's prior. Most codes are unmeasured — that does not make their findings wrong, only unverified. Report it rather than inflating or discounting the finding. - Read
parserTierwhen a finding concerns source code.regex-fallbackorfallback-languagemeans no syntax tree was available for that file, so absence of a finding there is weak evidence; the owning validator also reportspartial. - Read
checkCoveragebefore writing any "all clear".passed/totalcounts checks and its denominator excludes every validator that could not run.
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 2333952f1c32
- 9d ago Changed 614d07376b51
- 11d ago Changed 4f163c782857
- 12d ago Changed a136a5139e95
- 21d ago Changed · +6 lines 15f1bc2ee9e0
- 22d ago Changed · +8 lines e57e42678f7e
- 1mo ago Changed · +35 lines 4008c9b83a0f
- 1mo ago Changed 9aae3f12780b
- 1mo ago Changed cfe76d2544a3
- 1mo ago First seen · 185 lines · 53 tokens per session scan A c901d44b8598
docguard-guard is a skill published in the GitHub repository raccioly/docguard (32 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 2,753 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".