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/sync)<a href="https://agentmods.dev/commands/raccioly/docguard/sync"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/sync/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/sync"><img src="https://agentmods.dev/badge/commands/raccioly/docguard/sync.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.00023 | $0.00552 |
| Opus 5.5 | $0.00009 | $0.00221 |
| Sonnet 5.5 | $0.00005 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
sync 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DocGuard Sync
Keep the documentation memory ALWAYS UP TO DATE. Sync re-derives every code-truth
section (endpoints, entities, screens, tech stack, env vars) and refreshes the
matching source=code sections of existing canonical docs in place. Human prose
is never touched — it lives outside markers or in source=human sections.
When a code section changes, the prose sections in that doc are flagged for agent review.
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).
Execution
- Preview what will change (dry run, never writes):
docguard sync $ARGUMENTS
- If only
source=codesections are stale, apply the mechanical refresh:
docguard sync --write $ARGUMENTS
- For each "prose to review" line, read the affected doc and update the surrounding human-written section to match the new code reality (e.g. if the endpoints table grew, update the API overview prose). Then re-run guard:
docguard guard
Flags
--since <ref>— also report which code files changed since this git ref (context for prose updates).--write— apply the mechanical refreshes. Default is a dry-run preview.--force— sync unmarked default-path docs. It never bypasses mapped-document section ownership.--format json— machine-readable output (updates,reviews,skipped).
When to use
- Before opening a PR:
docguard sync --since mainto refresh any stale sections. - On a pre-commit hook: auto-keep the memory current.
- After a big refactor: confirm the doc map still matches the territory.
Triage glyphs
↻mechanically refreshed (code section updated)•stale (will refresh with--write)🤖prose to review — open the doc, update the relevant human-written section
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 c2a0ab077887
- 3d ago Changed bac5dfe15994
- 5d ago Changed ec3fd71b0614
- 6d ago Changed 5b313b7d627c
- 15d ago Changed · +6 lines 89882a1a9240
- 1mo ago Changed adf7667cdaac
- 1mo ago Changed · +4 tokens per session 90edec28a8db
- 1mo ago First seen · 63 lines · 19 tokens per session scan A 065d8cb2f4b8
sync is a command published in the GitHub repository raccioly/docguard (32 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 552 once invoked, about $0.0001 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.