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/integration-skills/integration-testingnpx skills add elastic/integration-skills --skill integration-testinggit clone --depth 1 https://github.com/elastic/integration-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.00052 | $0.00994 |
| Opus 5 | $0.00026 | $0.00497 |
| Sonnet 5 | $0.00010 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
integration-testing 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 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.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
integration-testing
When to use
Load this skill whenever tasks include:
- authoring or debugging pipeline test fixtures (
.log/.jsoninputs,*-expected.jsonoutput, config files) - setting up or debugging system tests (
_dev/test/system/,_dev/deploy/, mock APIs, 0-hits failures) - writing script tests for failure paths, API error handling, or package upgrades
When not to use
Do not use this skill as the primary guide for:
- ingest pipeline processor design and architecture (
ingest-pipelines) - CEL program development (
cel-programs) - broad elastic-package command selection and stack lifecycle (
elastic-package-cli)
Reference files — load the one that matches your test type
| Test type | Load when | Reference file |
|---|---|---|
| Pipeline tests | Writing fixtures, config files, expected output, debugging pipeline test failures | references/pipeline-testing.md |
| System tests (generic) | Always load for any system test work — config fields, commands, teardown, debugging | references/system-testing.md |
| Script tests | txtar failure/error tests, upgrade tests, mock services embedded in txtar | references/script-testing.md |
System test input-specific references
In addition to the generic system-testing.md, load the reference file matching your data stream's input type:
| Input type | Reference file |
|---|---|
cel |
references/system-testing-cel.md |
tcp, udp |
references/system-testing-tcp-udp.md |
http_endpoint |
references/system-testing-http-endpoint.md |
logfile, filestream |
references/system-testing-logfile.md |
kafka, gcp-pubsub |
references/system-testing-kafka-pubsub.md |
aws-s3, gcs, azure-blob-storage, azure-eventhub |
references/system-testing-cloud-skip.md |
When an integration supports multiple input types, load the generic reference plus each applicable input-type reference.
When working across multiple test types in one task (e.g. creating a new data stream end-to-end), load all applicable reference files.
What ships with it
11 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.
- references/builder-setup-subagent-guidance.md 13 KB
- references/builder-system-test-subagent-guidance.md 11 KB
- references/pipeline-testing.md 12 KB
- references/script-testing.md 19 KB
- references/system-testing-cel.md 3.4 KB
- references/system-testing-cloud-skip.md 3.4 KB
- references/system-testing-http-endpoint.md 3.4 KB
- references/system-testing-kafka-pubsub.md 3.7 KB
- references/system-testing-logfile.md 3.2 KB
- references/system-testing-tcp-udp.md 3.4 KB
- references/system-testing.md 7.5 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.
- 2d ago First seen · 64 lines · 52 tokens per session scan A 3b07764d70d7
integration-testing is a skill published in the GitHub repository elastic/integration-skills (15 stars, last pushed 5d ago), licensed Apache-2.0. It adds 52 tokens to every session and 994 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…