ref-markdown-documentation-standards

ref-markdown-documentation-standards is a skill for Claude Code, Codex from deephaven/deephaven-mcp. It costs 39 tokens per session (1,666 once invoked), scanned C, original, Apache-2.0.

A set of formatting rules for Markdown documentation, including JSON examples, JSON5 examples, placeholders, and copy-ready code blocks. Markdown is a plain-text format used to write structured documents.

In plain words
What is it for?
Use it when creating or editing Markdown files that contain configuration examples or instructions for users and developers.
Why use it?
It prevents documentation examples from being invalid, misleading, or difficult to copy into configuration files.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/deephaven/deephaven-mcp/ref-markdown-documentation-standards
Any agent
npx skills add deephaven/deephaven-mcp --skill ref-markdown-documentation-standards
Clone the repo
git clone --depth 1 https://github.com/deephaven/deephaven-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ref-markdown-documentation-standards

README.md
[![agentmods](https://agentmods.dev/badge/skills/deephaven/deephaven-mcp/ref-markdown-documentation-standards.svg)](https://agentmods.dev/skills/deephaven/deephaven-mcp/ref-markdown-documentation-standards)
Your own site
<a href="https://agentmods.dev/skills/deephaven/deephaven-mcp/ref-markdown-documentation-standards"><img src="https://agentmods.dev/badge/skills/deephaven/deephaven-mcp/ref-markdown-documentation-standards.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,666 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.01666
Opus 5 $0.00019 $0.00833
Sonnet 5 $0.00008 $0.00333
Haiku 4.5 $0.00004 $0.00167

Measured 4d ago against content hash 1033716b0e52, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

ref-markdown-documentation-standards scanned grade C with 1 finding 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 4d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

- American English spelling throughout — apply `ref-python-coding-practices` rule 8 (statement, enforcement, and ignore convention). Markdown-specific delta: in prose, the ignore comment takes the HTML-comment form `<!--
.agents/skills/ref-markdown-documentation-standards/SKILL.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation Standards

JSON/JSON5 Code Blocks in Markdown

  1. Use only ASCII characters in JSON/JSON5 code blocks: JSON examples in markdown files must contain only ASCII characters (character codes 0-127). Do not use emoji or other non-ASCII Unicode characters (such as ✅, ❌, ⚠️) within JSON/JSON5 code blocks, even in comments.

    Rationale: Users copy-paste these examples into configuration files. Many JSON parsers and text editors have issues with non-ASCII characters, leading to parsing errors.

    Correct:

    // community/sessions/local_dev.json
    {
      "host": "localhost",
      "port": 10000,
      "auth": {
        "credentials": {
          "type": "psk",
          "token": "${env:DH_AUTH_TOKEN}"  // RECOMMENDED: source the token from an env var
        }
      }
    }
    

    Incorrect:

    // community/sessions/local_dev.json
    {
      "host": "localhost",
      "port": 10000,
      "auth": {
        "credentials": {
          "type": "psk",
          "token": "${env:DH_AUTH_TOKEN}"  // ✅ RECOMMENDED: source the token from an env var
        }
      }
    }
    
  2. **Use json5 for code blocks with comments**: If a JSON code block contains comments (// or /* */), mark it asjson5, not ```json. Standard JSON does not support comments.

    Correct:

    // This is a valid JSON5 comment
    {
      "key": "value"  // Inline comment
    }
    

    Incorrect:

    // This will cause a parser error
    {
      "key": "value"
    }
    
  3. Validate JSON blocks: All code blocks marked as ```json must be valid, parseable JSON. Use a JSON validator to verify examples before committing.

General Documentation Standards

  1. Keep examples copy-paste ready: All code examples should work when copied directly from documentation without modification (except for placeholder values like passwords, URLs, etc.).

  2. Use clear placeholder values: Make it obvious what values need to be replaced:

    • Good: "password": "your-password-here", "host": "your-server.example.com"
    • Bad: "password": "xxxx", "host": "server"

Read the full file on GitHub · 142 lines

Changes

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.

  1. 4d ago First seen · 142 lines · 39 tokens per session scan C 1033716b0e52

Subscribe to this mod's changes

ref-markdown-documentation-standards is a skill published in the GitHub repository deephaven/deephaven-mcp (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,666 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens