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 setting-up-wide-events-storegit 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/setting-up-wide-events-store)<a href="https://agentmods.dev/skills/adammiribyan/wide_events/setting-up-wide-events-store"><img src="https://agentmods.dev/badge/skills/adammiribyan/wide_events/setting-up-wide-events-store/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/setting-up-wide-events-store"><img src="https://agentmods.dev/badge/skills/adammiribyan/wide_events/setting-up-wide-events-store.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.00058 | $0.01233 |
| Opus 5 | $0.00029 | $0.00616 |
| Sonnet 5 | $0.00012 | $0.00247 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
setting-up-wide-events-store 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 12d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setting up the Wide Events store
This is the guided path from "wide_events is installed" to "production
requests are queryable." It wraps deterministic generator/checker code -
never hand-edit config/deploy.yml or .kamal/secrets yourself; every
mutation here is idempotent, so re-running any step (including this whole
skill) is always safe.
What to ask for
Exactly three things, nothing else:
- the SSH address (IP or DNS name) of the VM that will run the store;
- the public DNS hostname end users/agents will query through (no scheme, no path); and
- retention in days (default 30 if the human has no preference).
Steps
-
Generate the accessory.
bin/rails generate wide_events:store --host=<ssh-address> --hostname=<telemetry-hostname> --retention-days=<n>This edits
config/deploy.yml(accessory, app environment,telemetryandwide-events-backupaliases) and writes durable, gitignored tokens to.kamal/wide-events-ingest-tokenand.kamal/wide-events-query-token. If it refuses instead of editing (ambiguous YAML, a conflicting existing key), it prints a complete snippet - merge that by hand, then continue. -
Show the exact DNS record. Tell the human to point the telemetry hostname at the store host now, before deploying, so propagation happens in parallel with the next steps instead of after them.
-
Run the checker.
bin/rails wide_events:setup:checkThis is the same idempotent command at every stage - before the first deploy, while waiting on DNS, and after
kamal setup- so there is never a different command to remember. It reports one of five states:failed- a Kamal version/config problem, or a host-directory permission problem. Fix what the message says (it includes the exact one-time administrator command if root is needed to create the data directory) and re-run.needs_dns- DNS has not resolved yet. This is expected and resumable, not an error. Nothing generated is reverted or lost; re-running the same command later picks up exactly where it left off. Wait for propagation and run it again.ready_to_deploy- DNS is good and the store isn't answering yet. Proceed to step 4.degraded- the store is routable but not accepting writes (usually low disk space). Do not proceed; investigate on the host.healthy- already fully deployed and working (useful if you're re-running this skill against an existing setup).
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.
- 12d ago First seen · 121 lines · 58 tokens per session scan A f4c16a0a681b
setting-up-wide-events-store is a skill published in the GitHub repository adammiribyan/wide_events (11 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,233 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
observability-stack-setup
Bootstrap end-to-end observability with OpenTelemetry traces, metrics, and logs, including GenAI LLM span conventions, dashboards, alerts, and SLO/SLI definition.
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…
otel-collector-builder
Build custom OpenTelemetry Collector distributions with OCB (OpenTelemetry Collector Builder). Use when authoring or debugging a builder manifest (builder.yaml), choosing component and provider versions, building a collector that bundles a custom or out-of-distribution component, setting up CI or Docker builds of a…
signoz-writing-clickhouse-queries
Write raw ClickHouse SQL for a SigNoz dashboard panel: timeseries, value, or table widgets that the builder UI cannot express (custom joins, window functions, regex extraction over log bodies, aggregations beyond builder syntax). Trigger when the user explicitly asks for a "ClickHouse query", a "raw SQL panel", a…
signoz-setting-up-observability
Run the full end-to-end observability setup for a service after its telemetry is already flowing into SigNoz: sequence SLI/SLO capture, data exploration (RED/USE), focused dashboards, saved Explorer views, burn-rate and absent-data alerts, and a tuning loop into one opinionated, SLO-aware workflow. Make sure to use…
signoz-mcp-setup
Initialize or repair SigNoz MCP server configuration for Agent Plugins v1, Claude Code, Codex, Cursor, VS Code/GitHub Copilot, Claude Desktop, Gemini CLI, Devin CLI, Grok Build, Windsurf, Zed, Antigravity CLI, OpenCode, or another MCP client. Use this skill before any SigNoz docs, query, dashboard, alert, or view…