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/diagnosegit 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.00010 | $0.00289 |
| Opus 5 | $0.00005 | $0.00144 |
| Sonnet 5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
diagnose 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 Diagnose
Runs guard validation, analyzes failures, and generates AI-ready prompts to fix documentation issues.
User Input
$ARGUMENTS
Steps
- Run DocGuard diagnose on the current project:
npx --yes docguard-cli@latest diagnose $ARGUMENTS
-
Review the output:
- Issues found — categorized as errors or warnings
- Remediation plan — ordered list of fix commands
- AI-ready prompt — copy/paste to your AI agent for automated fixes
-
For multi-perspective analysis, add
--debateto get three-agent prompts (Advocate/Challenger/Synthesizer).
Flags
--format json— Output as JSON--debate— Generate multi-perspective AI prompts--dir <path>— Run on a different directory
Research
Inspired by AITPG (IEEE TSE 2026) multi-agent prompting and TRACE (IEEE TMLCN 2026) calibrated quality evaluation.
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 · 44 lines · 10 tokens per session scan A a614b91a27dc
diagnose is a command published in the GitHub repository raccioly/docguard (27 stars, last pushed 5d ago), licensed MIT. It adds 10 tokens to every session and 289 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.