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 adammiribyan/wide_events --skill debugging-with-wide-eventsgit clone --depth 1 https://github.com/adammiribyan/wide_eventsWrote 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/adammiribyan/wide_events/debugging-with-wide-events)<a href="https://agentmods.dev/skills/adammiribyan/wide_events/debugging-with-wide-events"><img src="https://agentmods.dev/badge/skills/adammiribyan/wide_events/debugging-with-wide-events/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/adammiribyan/wide_events/debugging-with-wide-events"><img src="https://agentmods.dev/badge/skills/adammiribyan/wide_events/debugging-with-wide-events.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00054 | $0.01531 |
| Opus 5 | $0.00027 | $0.00766 |
| Sonnet 5 | $0.00011 | $0.00306 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
debugging-with-wide-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 11d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging with wide events
Every request and job execution is one row: the OTel root span with
main = true, carrying route, user/account ids, build SHA, status, error
state, per-dependency query counts, cache hits, feature flags, phase
timings, and whatever domain attributes the app set. Cross-request analysis
never needs child spans: filter main = true and aggregate.
Where the rows live
- Wide Events store (bundled DuckDB accessory): the
wide_eventstable.route,job_class,status,error,request_id,duration_ms,kind,deployment, andsourceare promoted columns; everything else the app set is in theattributesVARIANT column, read withattributes['key.name']. A VARIANT cannot be returned as-is, so cast it to the type you want:attributes['exception.type']::VARCHAR,attributes['account.id']::BIGINT,attributes['feature_flag.new_ui']::BOOLEAN.IS NULLworks without a cast. Query it withkamal telemetry(an interactive prompt, or pipe SQL to it non-interactively) - never SSH in and open the database file directly. - ClickHouse (HyperDX/ClickStack default schema): the
otel_tracestable; wide-event attributes are in theSpanAttributesmap, resource attributes (build, host, environment) inResourceAttributes. Adapt table and column names to the backend at hand. - Log sink deployments: one JSON object per line; query with your log store's JSON operators.
Filter by environment when staging and production share storage (the DuckDB store is single-tenant per deployment, so this mainly applies to the ClickHouse/log backends).
Operational health (DuckDB store)
SELECT * FROM wide_events_store_status; is the one-row operational view:
row counts for the last hour/day, oldest/newest received event, database and
free-disk bytes, write-readiness and its reason, last checkpoint/retention/
backup times and errors, and the store/protocol/DuckDB versions. Check this
first when bin/rails wide_events:setup:check reports degraded, or before
trusting a "no events" result - it tells you whether anything has arrived at
all.
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.
- 11d ago First seen · 160 lines · 54 tokens per session scan A 469fd4569f44
debugging-with-wide-events is a skill published in the GitHub repository adammiribyan/wide_events (11 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 1,531 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.
Other skills, from other repositories
phoenix-observability
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
observability
Use when instrumenting a service from the inside so an incident can be explained from telemetry alone — wiring OpenTelemetry logs, metrics and traces, standing up a Collector, exporting via OTLP, and defining telemetry-driven alerts. NOT outside-in uptime probes, on-call rotation, or who-gets-paged (that is…
phoenix-observability
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
signoz-investigating-alerts
Diagnose why a SigNoz alert fired by correlating the alert's own signal with neighbor signals (error rate, latency, throughput, CPU/memory), traces, and logs around the fire window, and rank likely causes. Make sure to use this skill whenever the user asks "why did this alert fire", "what caused alert X", "investigate…
phoenix-observability
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.