What is edgedelta-reference?

A reference guide to EdgeDelta version 3 pipeline components. EdgeDelta is a system for collecting, processing and sending observability data through configurable pipelines.

Use it to find component syntax, parameters, validation rules, compatibility details and documentation links for EdgeDelta pipeline configurations.

It saves time looking up which sources, processors and destinations are supported and how their settings must be written.

edgedelta-reference — Skill by edgedelta

Install

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.

agentmods

npx agentmods add skills/edgedelta/claude-code-plugins/edgedelta-reference

Any agent

npx skills add edgedelta/claude-code-plugins --skill edgedelta-reference

Clone the repo

git clone --depth 1 https://github.com/edgedelta/claude-code-plugins

Made for: Claude Code, Codex.

Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,325 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00087	$0.04325
Opus 5	$0.00044	$0.02162
Sonnet 5	$0.00017	$0.00865
Haiku 4.5	$0.00009	$0.00432

Measured yesterday against content hash 5b1e85be8f87, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

edgedelta-reference 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 yesterday.

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.

plugins/edgedelta-reference/skills/edgedelta-reference/SKILL.md · 526 lines

How it starts

The opening of the file, as written. The whole thing — 526 lines — stays where its author put it; the contents beside it link to each section on GitHub.

EdgeDelta Reference Skill

You are an expert reference guide for EdgeDelta pipeline v3 components. This skill provides comprehensive quick-lookup documentation for sources, processors, and destinations with copy-paste examples and documentation links.

Component Categories

Category	Count	Reference
Sources	30	references/sources/index.md
Processors	38	references/processors/
Destinations	54	references/destinations/index.md

When to Use This Skill

Activate this skill when:

User asks about EdgeDelta processors, inputs, outputs, or sources
User asks "what sources does EdgeDelta support?" or "what destinations are available?"
User needs processor specifications, parameters, or YAML syntax
User asks "what processors are available" or "how do I use X processor"
User is building a pipeline and needs component syntax
User asks for examples of any pipeline node (source, processor, destination)
User asks "how do I configure a [Kafka/Loki/Splunk/etc] destination?"
Another skill (like edgedelta-pipelines) needs component reference lookup
User wants to know which processors are sequence-compatible
User wants to look up a documentation link for any EdgeDelta component

Do NOT Use This Skill When

User wants to deploy a complete pipeline → use edgedelta-pipelines skill instead
User asks about EdgeDelta dashboards → use edgedelta-dashboards skill
User asks about OTTL functions or syntax → use edgedelta-ottl skill instead
User needs OTTL function reference (ParseJSON, EDXRedis, etc.) → use edgedelta-ottl skill
General observability questions without EdgeDelta context

Core Capabilities

Quick Lookup: Instant copy-paste snippets for all 38 processors
Complete Coverage: 30 sources, 38 processors, 54 destinations with docs links
Detailed References: In-depth documentation for 23 core processors (400-1000+ lines each)
Source Code Validated: Processor references cross-checked with EdgeDelta source code
Production Ready: Includes real-world examples, validation rules, common pitfalls, and best practices
Documentation Links: Every component links to docs.edgedelta.com

Read the full file on GitHub · 526 lines

Files

What ships with it

45 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.

Changes

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.

yesterday First seen · 526 lines · 87 tokens per session scan A 5b1e85be8f87

Subscribe to this mod's changes

edgedelta-reference is a skill published in the GitHub repository edgedelta/claude-code-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 87 tokens to every session and 4,325 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.

Frontend Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens