agentmods.dev

span-timeline-events

Instructions for adding events to OpenTelemetry span timelines. OpenTelemetry is a standard for recording what software is doing, and a span represents one timed operation in a trace.

In plain words
What is it for?
Use it when adding, changing, or debugging events shown in the trace view, including their stored format, names, timestamps, and visibility.
Why use it?
It prevents timeline events from being stored incorrectly or silently omitted, and ensures they appear on the correct operation in the trace viewer.

Skill for Claude CodeCodex

16k 2d ago A scan 52 tokens original Apache-2.0
View the source file triggerdotdev/trigger.dev
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/triggerdotdev/trigger.dev/span-timeline-events
Any agent
npx skills add triggerdotdev/trigger.dev --skill span-timeline-events
Clone the repo
git clone --depth 1 https://github.com/triggerdotdev/trigger.dev

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,064 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.

ModelPer sessionOnce invoked
Fable 5 $0.00052 $0.01064
Opus 5 $0.00026 $0.00532
Sonnet 5 $0.00010 $0.00213
Haiku 4.5 $0.00005 $0.00106

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

Security

Grade A, and why

span-timeline-events 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.

.claude/skills/span-timeline-events/SKILL.md · 79 lines

How it starts

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

Span Timeline Events

The trace view's right panel shows a timeline of events for the selected span. These are OTel span events rendered by app/utils/timelineSpanEvents.ts and the SpanTimeline component.

How They Work

  1. Span events in OTel are attached to a parent span. In ClickHouse, they're stored as separate rows with kind: "SPAN_EVENT" sharing the parent span's span_id. The #mergeRecordsIntoSpanDetail method reassembles them into the span's events array at query time.
  2. The timeline only renders events whose name starts with trigger.dev/ - all others are silently filtered out.
  3. The display name comes from properties.event (not the span event name), mapped through getFriendlyNameForEvent().
  4. Events are shown on the span they belong to - events on one span don't appear in another span's timeline.

ClickHouse Storage Constraint

When events are written to ClickHouse, spanEventsToTaskEventV1Input() filters out events whose start_time is not greater than the parent span's startTime. Events at or before the span start are silently dropped. This means span events must have timestamps strictly after the span's own startTimeUnixNano.

Timeline Rendering (SpanTimeline component)

The SpanTimeline component in app/components/run/RunTimeline.tsx renders:

  1. Events (thin 1px line with hollow dots) - all events from createTimelineSpanEventsFromSpanEvents()
  2. "Started" marker (thick cap) - at the span's startTime
  3. Duration bar (thick 7px line) - from "Started" to "Finished"
  4. "Finished" marker (thick cap) - at startTime + duration

The thin line before "Started" only appears when there are events with timestamps between the span start and the first child span. For the Attempt span this works well (Dequeued -> Pod scheduled -> Launched -> etc. all happen before execution starts). Events all get lineVariant: "light" (thin) while the execution bar gets variant: "normal" (thick).

Trace View Sort Order

Read the full file on GitHub · 79 lines

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.

  1. yesterday First seen · 79 lines · 52 tokens per session scan A 83a6d1b7a8da

Subscribe to this mod's changes

span-timeline-events is a skill published in the GitHub repository triggerdotdev/trigger.dev (16,165 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,064 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-30.

DebuggingFrontendOrchestrationProductivityautomationbackground-jobsnextjsschedulerserverless
Related

Other skills, from other repositories

workflow

Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue"…

vercel/workflow · 84 tokens

migrating-workflow-v4-to-v5

Upgrades an app from Workflow SDK 4.x to 5.0. Use when bumping the workflow / @workflow/ dependencies to v5, or when hitting removed v4 APIs — runStep, stepEntrypoint, workflow/internal/private, @workflow/core/private, writeToStream / closeStream / readFromStream on a World, world.steps.get without a runId…

vercel/workflow · 161 tokens

migrating-world-v4-to-v5

Upgrades a custom Workflow SDK World implementation from the v4 spec to v5. Use when a package implements the World interface from @workflow/world and is moving to 5.x — event IDs that are ULIDs rather than slot positions, Event id is not slot-numbered at replay time, a specVersion the runtime refuses, writeToStream /…

vercel/workflow · 166 tokens

migrating-to-workflow-sdk

Migrates Temporal, Inngest, Trigger.dev, and AWS Step Functions workflows to the Workflow SDK. Use when porting Activities, Workers, Signals, step.run(), step.waitForEvent(), Trigger.dev tasks / wait.forToken / triggerAndWait, ASL JSON state machines, Task/Choice/Wait/Parallel states, task tokens, or child workflows.

vercel/workflow · 81 tokens

workflow-init

Install and configure Vercel Workflow SDK before it exists in nodemodules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro, SvelteKit, or Vite.

vercel/workflow · 78 tokens

internal-dev-workbench

Spin up a portless + tmux dev session for the Workflow SDK that gives each git worktree isolated . .localhost URLs for the Next.js workbench and the observability UI, plus a Claude statusline that surfaces those URLs. Use only when the user asks for a "portless dev session", a "tmux dev layout for workflow"…

vercel/workflow · 122 tokens