Borrowing it
Nothing to install: this file belongs to deephaven/deephaven-mcp. 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/deephaven/deephaven-mcp/main/.agents/skills/docs-accuracy/SKILL.mdgit clone --depth 1 https://github.com/deephaven/deephaven-mcpWrote 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/deephaven/deephaven-mcp/docs-accuracy)<a href="https://agentmods.dev/skills/deephaven/deephaven-mcp/docs-accuracy"><img src="https://agentmods.dev/badge/skills/deephaven/deephaven-mcp/docs-accuracy/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/deephaven/deephaven-mcp/docs-accuracy"><img src="https://agentmods.dev/badge/skills/deephaven/deephaven-mcp/docs-accuracy.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.00064 | $0.00484 |
| Opus 5.5 | $0.00026 | $0.00194 |
| Sonnet 5.5 | $0.00013 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
docs-accuracy 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 1mo 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
When to use this vs. docs-improve: use docs-accuracy for surgical correctness-only fixes against a single document. Use docs-improve for a full review that may also reorganize sections, fix link rot, or add missing content.
Before editing, load ref-documentation-roles and confirm that proposed fixes stay inside the document's role. When a fact is wrong in this doc but right in another, fix it here — do not delete it and link out unless the role of this doc says it should not have been here in the first place. Self-contained docs (currently SECURITY.md) must remain self-contained.
For the specified document, verify every factual claim against the source code. Check:
- Commands and flags: run the command or read
--helpoutput; confirm flags exist and do what the doc says - File paths: confirm each path exists in the repo
- Config keys and values: check against the actual config schema or parser in the source
- API names, function signatures, and module paths: grep or read the source
- Code examples: verify syntax is valid and matches the actual API; apply the
ref-markdown-documentation-standardsskill for JSON/JSON5 code block and placeholder formatting - Port numbers, URLs, environment variable names: confirm against source or config
- Output value vocabularies: when the doc documents the values of a tool / CLI output field (e.g., enumerating
--origin static|dynamic|discoveredor sample JSON values), applyref-output-serialization-conventionsand confirm the documented values match what the code emits - Spelling: apply
ref-markdown-documentation-standardsProse conventions; verify withuv run codespell <file>
For each inaccuracy found, report what the document says, what it should say, and fix it directly in the document.
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.
- 1mo ago First seen · 22 lines · 64 tokens per session scan A b4ab4cd135a8
docs-accuracy is a skill published in the GitHub repository deephaven/deephaven-mcp (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 64 tokens to every session and 484 once invoked, about $0.0003 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…