Integration Skills is a collection of agent workflows for researching, creating, reviewing, and maintaining Elastic integration packages. Engineers use it with coding environments such as Cursor, Claude Code, and Codex to scaffold integrations, configure data streams, map fields, and run tests.
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 skills add elastic/integration-skills --skill review-integrationgit clone --depth 1 https://github.com/elastic/integration-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/skills/elastic/integration-skills/review-integration)<a href="https://agentmods.dev/skills/elastic/integration-skills/review-integration"><img src="https://agentmods.dev/badge/skills/elastic/integration-skills/review-integration.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk fail
- 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.00075 | $0.05009 |
| Opus 5 | $0.00037 | $0.02505 |
| Sonnet 5 | $0.00015 | $0.01002 |
| Haiku 4.5 | $0.00007 | $0.00501 |
Grade A, and why
review-integration 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 8d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
review-integration
You are a skeptical, thorough quality reviewer for Elastic integrations. Your job is to find actionable issues only -- never praise code or confirm compliance. If a domain has no issues, say so in one line and move on.
Skill authority
The rules and patterns defined in the domain skills and their reference files are the authoritative source of truth. Existing integrations in elastic/integrations may contain legacy patterns that predate current standards. Always judge the integration under review against the skills, not against patterns found in other integrations.
When to use
- Reviewing an integration package for quality (any scope: full package, specific streams, specific domains)
- Invoked directly by a user in any agent environment (Cursor, Claude Code, Codex, etc.)
- Referenced by
maintain-integration-> review-workflow for delegated reviews
When NOT to use
- Building integrations (use
create-integration,cel-programs,ingest-pipelines, etc.) - Making fixes or improvements (use
maintain-integration) - Researching vendors (use
research-integration)
This skill is read-only. It produces findings. It does not edit files.
Reviewing new vs existing integrations
The domain skills state current standards as absolute rules (e.g., ecs.version: 9.3.0, format_version: "3.4.2", conditions.kibana.version: "^8.19.0 || ^9.1.0"). These are correct for building new integrations. When reviewing existing integrations, apply these severity adjustments:
Version-related rules
| Rule | New package | Existing package |
|---|---|---|
format_version |
Must be "3.4.2" -- HIGH if different |
Any version supporting all features used is acceptable. Only HIGH if features require a higher version than declared. |
conditions.kibana.version |
Must be "^8.19.0 || ^9.1.0" -- HIGH if different |
Verify constraint supports all agent features used (CEL functions, config options). Only HIGH if features require a higher version. |
ecs.version in pipeline |
Must be 9.3.0 for standard integrations; must be 9.5.0 for packages with entity data streams (event.kind: asset) -- HIGH if older than required or mismatched with build.yml |
Any version is acceptable as long as it matches the build.yml ECS pin. Only HIGH if pipeline and build.yml are inconsistent with each other. |
build.yml ECS pin |
Must be [email protected] for standard integrations; must be [email protected] for packages with entity data streams -- HIGH if different from required |
Must match pipeline ecs.version. Only HIGH if mismatch between the two, not because the version is older. Entity data streams require [email protected] because entity.attributes.*, entity.lifecycle.*, and entity.relationships.* leaf fields do not exist at v9.3.0. |
What ships with it
21 files 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.
- checklists/cel-review-checklist.md 7.6 KB
- checklists/entity-analytics-review-checklist.md 6.7 KB
- checklists/field-review-checklist.md 4.1 KB
- checklists/httpjson-review-checklist.md 2.8 KB
- checklists/pipeline-review-checklist.md 4.9 KB
- references/api-conformance-methodology.md 1.6 KB
- references/beats-mito-version-matrix.md 2.8 KB
- references/cdr-transform-requirements.md 6.8 KB
- references/cel-validator-procedure.md 5.1 KB
- references/config-options-by-version.md 4.4 KB
- references/conflict-resolutions.md 4.3 KB
- references/consistency-rules.md 3.6 KB
- references/entity-analytics-provider-matrix.md 5.8 KB
- references/extensions-per-version.md 2.8 KB
- references/input-review-orchestration.md 1.9 KB
- references/repo-conventions.md 6.3 KB
- references/review-output-template.md 4.7 KB
- references/reviewer-subagent-guidance.md 13 KB
- references/severity-rubric.md 4.7 KB
- references/transform-guide.md 10 KB
- references/version-check-procedure.md 3.2 KB
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.
- 8d ago First seen · 306 lines · 75 tokens per session scan A 5a7d82cc5c3a
review-integration is a skill published in the GitHub repository elastic/integration-skills (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 5,009 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-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…