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/ref-cli-help-standards/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/ref-cli-help-standards)<a href="https://agentmods.dev/skills/deephaven/deephaven-mcp/ref-cli-help-standards"><img src="https://agentmods.dev/badge/skills/deephaven/deephaven-mcp/ref-cli-help-standards/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/ref-cli-help-standards"><img src="https://agentmods.dev/badge/skills/deephaven/deephaven-mcp/ref-cli-help-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.03927 |
| Opus 5.5 | $0.00023 | $0.01571 |
| Sonnet 5.5 | $0.00012 | $0.00785 |
| Haiku 4.5 | $0.00006 | $0.00393 |
Grade A, and why
ref-cli-help-standards 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Help Standards
The dhcli CLI is described by three surfaces from two authored sources: in-code help renders both the --help text and the agents-manifest node — a HelpSpec on the root and every leaf command, a function docstring on each noun group (split into manifest summary/description by _split_help_text; see Help-content contract, Group commands) — and docs/CLI.md is written by hand. Help text is plain text rendered verbatim by click in the terminal, so it carries no reStructuredText markup. Every leaf command's help follows a fixed section contract so a human or an AI agent can operate the command without reading the source or docs/CLI.md.
1. Three surfaces, two sources
| Surface | Role | Canonical source | Edited via |
|---|---|---|---|
docs/CLI.md |
Exhaustive reference | docs/CLI.md |
docs-improve / docs-accuracy (ref-documentation-roles) |
--help text |
Self-sufficient per-command help | the command's HelpSpec (cli/_help.py, rendered by build_help) |
cli-help-improve / cli-help-accuracy |
| agents manifest | Machine surface for agents (--help for AI agents) |
the same HelpSpec (cli/_manifest.py: build_summary_tree, build_manifest, describe_command); wired into commands by cli/_commands/agents.py |
cli-help-improve / cli-help-accuracy |
Consistency rule. --help and the agents manifest render from the one HelpSpec, so they cannot drift from each other — the surface to reconcile by hand is docs/CLI.md: a command's flags, arguments, exit codes, error_codes, and output fields must match between the spec and the doc. Change one, update the other in the same edit. The contract tests in tests/cli/test_help_contract.py (per-command section coverage, parametrized over the live click tree), tests/cli/test__help.py (build_help rendering), and tests/cli/test__manifest.py (the manifest builders: cleanliness, node schema, content preservation) pin the spec side; tests/cli/_commands/test_agents.py pins the agents verbs' CLI behavior (output modes, config bypass, flag/verb equivalence). docs/CLI.md has no automated check — verify it by hand.
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 · 103 lines · 58 tokens per session scan A 947c025cdbe5
ref-cli-help-standards is a skill published in the GitHub repository deephaven/deephaven-mcp (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 58 tokens to every session and 3,927 once invoked, about $0.0002 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…