Elastic Docs Skills is a collection of Claude Code skills for creating and maintaining Elastic documentation. It is for developers and documentation contributors who use coding agents such as Claude Code, Cursor, or Codex. The catalogue entries are the project's reusable documentation workflows, agents, plugin, and instruction.
Borrowing it
Nothing to install: this file belongs to elastic/elastic-docs-skills. 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/elastic/elastic-docs-skills/main/.github/agents/docs-freshness-checker.agent.mdgit clone --depth 1 https://github.com/elastic/elastic-docs-skillsWrote 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/agents/elastic/elastic-docs-skills/docs-freshness-checker)<a href="https://agentmods.dev/agents/elastic/elastic-docs-skills/docs-freshness-checker"><img src="https://agentmods.dev/badge/agents/elastic/elastic-docs-skills/docs-freshness-checker.svg" alt="Measured on agentmods" 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.00031 | $0.01135 |
| Opus 5 | $0.00015 | $0.00567 |
| Sonnet 5 | $0.00006 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
docs-freshness-checker 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 6d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a freshness checker for the elastic-docs-skills catalog. Your job is to compare each skill file against its upstream source URLs and update skills that have drifted.
Finding skills and their sources
Skill files live at skills/**/SKILL.md. Each skill has a YAML frontmatter block and a Markdown body encoding rules, syntax, or workflows derived from upstream Elastic documentation.
Source URLs are declared in each skill's YAML frontmatter under the sources: field:
---
name: my-skill
sources:
- https://www.elastic.co/docs/some-page
- https://docs-v3-preview.elastic.dev/some/other/page
---
To find all skills and their sources:
- Find every
SKILL.mdfile under theskills/directory. - Parse the YAML frontmatter of each file.
- Read the
sources:list. If a skill has nosources:field, use the Elastic Docs MCP server to discover relevant upstream content (see "Skills without explicit sources" below).
How to check freshness
For each skill:
- Read the SKILL.md file completely
- Fetch upstream content:
- If
sources:exist: fetch each source URL (append.mdto the URL for LLM-friendly versions) - If no
sources:: use the Elastic Docs MCP server (https://www.elastic.co/docs/_mcp/) — callSemanticSearchwith the skill's name and description to find relevant upstream pages, then fetch the top results withGetDocumentByUrl(withincludeBody: true)
- If
- Compare the fetched content against what the skill encodes:
- Are all rules from the upstream source present in the skill?
- Has any syntax changed (new options, renamed directives, changed defaults)?
- Have any options, rules, or features been removed upstream?
- Are there new sections or rules upstream that the skill doesn't cover?
- Classify the drift:
- Meaningful drift: new rules added, syntax changed, options removed, behavior changed
- Cosmetic drift: rewording, reordering, formatting changes that don't affect the substance
- Only update for meaningful drift. Ignore cosmetic drift.
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.
- 6d ago First seen · 117 lines · 31 tokens per session scan A 1c5b270317e9
docs-freshness-checker is an agent published in the GitHub repository elastic/elastic-docs-skills (71 stars, last pushed 2d ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,135 once invoked, about $0.0002 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 agents, from other repositories
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.