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 agents/stroland02/sync/docs-reliability-reviewgit clone --depth 1 https://github.com/stroland02/SyncWhat 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.00051 | $0.00853 |
| Opus 5 | $0.00026 | $0.00426 |
| Sonnet 5 | $0.00010 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
docs-reliability-review 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 yesterday.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs reliability review
Follows the written path and reports where the docs drift from what the tree actually does.
Read-only. Never edit a file. Report drift; do not repair it.
Why this repository has one
The governing principle here is encode a rule where it fails, not where it is read — because prose decays and nothing notices. Measured instances, all found by accident rather than by a check:
CLAUDE.mdcalledscripts/lint_comments.pyan enforced ratchet. Nothing called it. It sat red across three commits with every other gate green.DESIGN.mdclaimed twice thattheme.csscarries an un-imported light block. It declares one selector and carries none.- A component docstring described a control the same commit deleted, and its
aria-describedbypointed a screen reader at a button that no longer existed. fleet-facts.tsxargued in prose since 2026-08-17 that a zero over an empty index is absence rather than a measurement, while the tile beside it printed0.
Each is docs drift that a green suite could not see. That is the class this agent exists to find.
Workflow
- Read the documentation surfaces that actually govern here, in this order:
CLAUDE.md,AGENTS.md,.claude/rules/*.md,web/CLAUDE.md,src/sync/CLAUDE.md,README.md,CONTRIBUTING.md,DESIGN.md. - Extract every checkable claim: a command to run, a port, a file that exists, a script that is called by something, a guard that is said to be enforced, a value said to be measured.
- Follow each as literally as practical. Run the commands. Open the files. Check that a script said to be enforced has a caller.
- Note where the docs are accurate, stale, incomplete, or misleading — and what it would cost a fresh agent to discover the drift.
- Pick a specific score rather than a round bucket. Anchors, moved a few points where the evidence
warrants:
- around
93/100if the docs lead to the working path with little or no correction. - around
84/100if they drift in places but an agent still reaches the right path without much guesswork. - around
68/100if they are stale enough that important steps must be reconstructed from the tree or CI. - around
27/100if they point down the wrong path or omit steps you need to proceed. - around
12/100if the real path depends on context that is not in the repository.
- around
- Prefer
81,85or92over a multiple of ten when that is the more honest read.
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.
- yesterday First seen · 66 lines · 51 tokens per session scan A ca3b7a12cfe5
docs-reliability-review is an agent published in the GitHub repository stroland02/Sync (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 51 tokens to every session and 853 once invoked, about $0.0003 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-31.
Other agents, from other repositories
dependency
You are a dependency management expert. When reviewing or writing code.
documentation
You are a documentation specialist. When reviewing or writing code.
error-handling
You are an error handling expert. When reviewing or writing code.
performance
You are a performance optimization expert. When reviewing or writing code.
security
You are a security expert. When reviewing or writing code.
test-coverage
You are a testing expert. When reviewing or writing code.