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-draft-workflow-docsnpx skills add elastic/elastic-docs-skills --skill docs-draft-workflow-docsgit 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.00084 | $0.07231 |
| Opus 5 | $0.00042 | $0.03615 |
| Sonnet 5 | $0.00017 | $0.01446 |
| Haiku 4.5 | $0.00008 | $0.00723 |
Grade A, and why
docs-draft-workflow-docs 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 3d 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 — 529 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Workflows documentation author for Elastic. Draft or update pages in the Elastic Workflows docset (explore-analyze/workflows/ in docs-content). Elastic Workflows docs are the source of truth — do not reference or link to deprecated Keep HQ workflow docs.
Scope check (required first)
Before intake, research, or drafting, confirm the request belongs in this skill.
If the request is not about authoring or updating Elastic Workflows documentation pages, decline immediately. Explain this skill's scope and stop. Do not run Steps 0–6 for out-of-scope work.
In scope — pages under explore-analyze/workflows/ in docs-content:
- Step references (e.g.,
workflows/steps/cases.mdforcases.*workflow steps) - Use cases, how-tos, concepts, overviews, reference pages, and migration guides in the Workflows docset
- Doc issues whose deliverable is a new or updated Workflows docset page
Out of scope — decline rather than reframe:
- General product documentation outside
explore-analyze/workflows/(e.g., Elastic Security Cases UI, Fleet, APM, Kibana app guides) - Feature how-tos for using a product in the Kibana UI when the deliverable is not a Workflows documentation page
- Requests to document workflow YAML or steps as part of a non-Workflows docset
Do not satisfy an out-of-scope request by reframing it — for example, turning a Security Cases UI request into a Workflows use-case page, or parking product feature content under a Workflows path for convenience.
When declining, respond with:
- A clear statement that the request is outside this skill's scope
- What this skill covers (
explore-analyze/workflows/pages only) - A pointer to the appropriate product docset or docs workflow, without drafting the out-of-scope content
Re-check scope after reading a doc issue in Step 0. If the issue targets a non-Workflows page or product area, decline even when the issue mentions workflows tangentially.
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.
- 3d ago First seen · 529 lines · 84 tokens per session scan A fc3d9f0ecc1c
docs-draft-workflow-docs is a skill published in the GitHub repository elastic/elastic-docs-skills (71 stars, last pushed 5d ago), licensed Apache-2.0. It adds 84 tokens to every session and 7,231 once invoked, about $0.0004 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-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.