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/edgedelta/claude-code-plugins/edgedelta-ottlnpx skills add edgedelta/claude-code-plugins --skill edgedelta-ottlgit clone --depth 1 https://github.com/edgedelta/claude-code-pluginsWhat 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.05309 |
| Opus 5 | $0.00026 | $0.02655 |
| Sonnet 5 | $0.00010 | $0.01062 |
| Haiku 4.5 | $0.00005 | $0.00531 |
Grade A, and why
edgedelta-ottl 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 — 577 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EdgeDelta OTTL & EDX Extensions Reference Skill
You are an expert reference guide for OTTL (OpenTelemetry Transformation Language) and EdgeDelta's custom EDX extensions. This skill provides comprehensive documentation, strict syntax validation, and quick-lookup references for all 124 OTTL functions used in EdgeDelta pipelines.
When to Use This Skill
Activate this skill when:
- User asks about OTTL syntax, operators, or language rules
- User needs documentation for OTTL functions (Set, ParseJSON, IsMatch, etc.)
- User asks about EDX extensions (EDXRedis, EDXCoalesce, EDXEnv, etc.)
- User is writing ottl_transform or ottl_filter processor configurations
- User encounters OTTL syntax errors and needs strict validation
- User asks "how do I write an OTTL statement?" or "what's the syntax for...?"
- User needs to understand OTTL conditionals, where clauses, or operators
- User wants to know which OTTL functions are available
- Another skill (like edgedelta-pipelines) needs OTTL function reference
Do NOT Use This Skill When
- User wants to deploy a complete pipeline → use
edgedelta-pipelinesskill instead - User asks about processors (not OTTL functions) → consult the EdgeDelta processor documentation at https://docs.edgedelta.com/processors
- User asks about dashboards → consult the EdgeDelta dashboard documentation at https://docs.edgedelta.com
- General observability questions without OTTL context
Core Capabilities
- OTTL Syntax Reference: Complete language rules (operators, conditionals, field access)
- Function Quick Lookup: Instant access to all 124 function signatures
- Strict Syntax Validation: Enforcement of critical rules (lowercase operators, single-line conditions)
- EDX Extensions: Comprehensive docs for all 23 EdgeDelta custom functions
- EDXRedis Deep Dive: 1000+ lines of documentation for Redis integration
- Cross-Skill Integration: Seamless reference from edgedelta-pipelines
Function Coverage
Standard OTTL Functions (101)
- Editors (14): Set, Append, DeleteKey, DeleteMatchingKeys, KeepKeys, Limit, MergeMaps, etc.
- Converters (50+): ParseJSON, Concat, IsMatch, ExtractPatterns, Split, Substring, etc.
- Type Checkers (8): IsBool, IsDouble, IsInt, IsList, IsMap, IsString, IsMatch, etc.
- Hashing (6): MD5, SHA1, SHA256, SHA512, FNV, MurmurHash3, etc.
- Time (15+): Now, Duration, Time, UnixMilli, UnixNano, FormatTime, TruncateTime, etc.
- XML (8): ParseXML, GetXML, InsertXML, RemoveXML, ConvertAttributesToElementsXML, etc.
What ships with it
25 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.
- MASTER_INDEX.md 66 KB
- references/edx/edx_delete_empty_values.md 6.0 KB
- references/edx/edx_delete_keys.md 4.8 KB
- references/edx/edx_delete_matching_keys.md 2.6 KB
- references/edx/edx_keep_keys.md 2.6 KB
- references/edx/edx_keep_matching_keys.md 1.0 KB
- references/edx/edx_map_keys.md 4.5 KB
- references/edx/edxcoalesce.md 15 KB
- references/edx/edxcode.md 7.1 KB
- references/edx/edxcompress.md 15 KB
- references/edx/edxdatatype.md 14 KB
- references/edx/edxdecode.md 12 KB
- references/edx/edxdecompress.md 8.1 KB
- references/edx/edxdecrypt.md 14 KB
- references/edx/edxencode.md 4.6 KB
- references/edx/edxencrypt.md 6.3 KB
- references/edx/edxenv.md 7.5 KB
- references/edx/edxextractpatterns.md 8.3 KB
- references/edx/edxhmac.md 9.8 KB
- references/edx/edxifelse.md 8.5 KB
- references/edx/edxparsekeyvalue.md 9.4 KB
- references/edx/edxredis.md 84 KB
- references/edx/edxunescapejson.md 7.6 KB
- references/syntax/syntax_guide.md 45 KB
- validation_rules.md 25 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 · 577 lines · 52 tokens per session scan A d92f84313c26
edgedelta-ottl is a skill published in the GitHub repository edgedelta/claude-code-plugins (2 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 5,309 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.