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/trace)<a href="https://agentmods.dev/commands/raccioly/docguard/trace"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/trace/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/trace"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/trace.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.00005 | $0.00460 |
| Opus 5.5 | $0.00002 | $0.00184 |
| Sonnet 5.5 | $0.00001 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
trace 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 Trace
Generate a requirements traceability matrix mapping canonical docs ↔ source code ↔ tests. Config-aware — respects .docguard.json exclusions and detects orphaned files.
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 trace on the current project:
docguard trace $ARGUMENTS
-
Review the matrix. Each canonical doc gets a coverage signal:
- TRACED — doc + source code + tests all linked
- PARTIAL — doc exists, source found, no test coverage
- UNLINKED — doc exists but no matching source code
- MISSING — doc not found
-
Orphaned files (exist but excluded from config) are flagged with cleanup instructions.
Standards
Maps against industry standards per document type:
| Document | Standard |
|---|---|
| ARCHITECTURE.md | arc42 / C4 Model |
| DATA-MODEL.md | C4 Component / ER (Chen) |
| TEST-SPEC.md | ISO/IEC/IEEE 29119-3 |
| SECURITY.md | OWASP ASVS v4.0 |
| ENVIRONMENT.md | 12-Factor App |
| API-REFERENCE.md | OpenAPI 3.1 |
Flags
--format json— Output as JSON--dir <path>— Run on a different directory
Research
Inspired by ISO/IEC/IEEE 29119 traceability requirements (Lopez et al., AITPG, IEEE TSE 2026).
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 21ae98aaa3e2
- 3d ago Changed 8dd5c7f5fd15
- 5d ago Changed 666512d31c6f
- 6d ago Changed 70db20fc4158
- 15d ago Changed · +6 lines 225696a294f7
- 1mo ago First seen · 57 lines · 5 tokens per session scan A c8fdee1b2cee
trace is a command published in the GitHub repository raccioly/docguard (32 stars, last pushed yesterday), licensed MIT. It adds 5 tokens to every session and 460 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.