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 skills/elastic/elastic-docs-skills/docs-validate-code-samplesnpx skills add elastic/elastic-docs-skills --skill docs-validate-code-samplesgit clone --depth 1 https://github.com/elastic/elastic-docs-skillsWhat 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.00055 | $0.03117 |
| Opus 5 | $0.00028 | $0.01558 |
| Sonnet 5 | $0.00011 | $0.00623 |
| Haiku 4.5 | $0.00006 | $0.00312 |
Grade A, and why
docs-validate-code-samples scanned grade A 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Infer the correct identifier from content: HTTP method line → `console`; starts with `{`/`[` → `json`; `key: value` lines → `yaml`; `curl`/`apt-get` → `bash`; `import`/`def`/`print(` → `python`; `public class` → `java`; How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code sample validator for Elastic documentation. Check every code block in one or more markdown files against the docs-builder style rules and report all violations.
Never modify documentation source files. Only analyze and report.
Step 1: Resolve files
Parse $ARGUMENTS for an optional --output <path> flag (strip it before continuing). Resolve the target:
- Single
.mdfile — analyze that file only. - Directory — find all
.mdfiles recursively withfind <dir> -name "*.md" -type f | sort. - Glob — expand with
bash -O globstar -c 'printf "%s\n" <glob>'. - No argument — ask: "Please provide a file path, directory, or glob pattern."
Step 2: Extract code blocks
For each file, use Grep with pattern ^``` to find fence line numbers, then Read the file to extract blocks. Also search for indented fences (^\s+```) to catch blocks inside list items.
- Skip blocks inside HTML comments (
<!-- ... -->). - Skip MyST directive blocks where the info string starts and ends with
{}(e.g.,```{note}).
For each block capture: opening line number, fence info string, language identifier (first word), attributes (remaining tokens), and body.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 218 lines · 55 tokens per session scan A 199459a011bc
docs-validate-code-samples is a skill published in the GitHub repository elastic/elastic-docs-skills (71 stars, last pushed 4d ago), licensed Apache-2.0. It adds 55 tokens to every session and 3,117 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
codex-docs-drift-scout
Install the AutoHub docs-drift Codex automation from signed AutoVault skill resources and audit its render fidelity with autovault doctor.
writing-docs
Skill "writing-docs" from Wade-DevCode/awesome-coding-skills-cn, covering 写文档, 何时用, 核心规则, 1. 开头讲"这是什么、解决什么问题、给谁用",30 秒能判断要不要继续读 and 2. 快速开始可复制即用:安装命令、最小示例,真实可跑.
pr-description
写 Pull Request 描述时使用。让 reviewer 快速理解与审查。.
writing-skills
How to write, split, and review docs/skills/ files in testsuite. Load when creating, editing, or deleting a skill.
bun-test
Complete guide to Bun's native test runner: writing tests, expect matchers, mocks, spies, lifecycle hooks, snapshots, code coverage, reporters, DOM testing, and test configuration.
bun-runtime-http
Covers Bun.serve, HTTP server configuration, routing, streaming responses, WebSockets, TLS/SSL, and middleware with Bun's native APIs.