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/j-morgan6/elixir-phoenix-guide/telemetry-essentialsnpx skills add j-morgan6/elixir-phoenix-guide --skill telemetry-essentialsgit clone --depth 1 https://github.com/j-morgan6/elixir-phoenix-guideWrote 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/j-morgan6/elixir-phoenix-guide/telemetry-essentials)<a href="https://agentmods.dev/skills/j-morgan6/elixir-phoenix-guide/telemetry-essentials"><img src="https://agentmods.dev/badge/skills/j-morgan6/elixir-phoenix-guide/telemetry-essentials.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.02808 |
| Opus 5 | $0.00016 | $0.01404 |
| Sonnet 5 | $0.00006 | $0.00562 |
| Haiku 4.5 | $0.00003 | $0.00281 |
Grade A, and why
telemetry-essentials 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 5d 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 — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telemetry Essentials
RULES — Follow these with no exceptions
- Use structured logging (
Logger.info("action", key: value)) — never string interpolation in log messages; structured logs are searchable and parseable - Attach telemetry handlers in
Application.start/2—:telemetry.attach/4with an existing handler ID returns{:error, :already_exists}, so it never double-attaches; attach at boot anyway, since handlers detach permanently if they raise and boot-time attachment gives them a stable lifecycle - Use
Ecto.Repotelemetry events for query monitoring — don't wrap every query manually; Ecto already emits events - Use
Phoenix.LiveDashboardin dev/staging — it's free observability with zero code - Tag telemetry events with metadata (user_id, request_id) — without correlation IDs, distributed traces are useless
- Never log at
:debuglevel in production — it includes query parameters and PII
Structured Logging
Structured logs can be filtered, searched, and aggregated. String-interpolated logs cannot.
Bad:
# String interpolation — unsearchable, inconsistent format
Logger.info("User #{user.id} created order #{order.id} for $#{order.total}")
Logger.error("Failed to process payment for user #{user.id}: #{inspect(reason)}")
Good:
# Structured logging — searchable, parseable by log aggregators
Logger.info("Order created", user_id: user.id, order_id: order.id, total: order.total)
Logger.error("Payment failed", user_id: user.id, reason: inspect(reason))
Keyword data goes to Logger metadata and is dropped unless whitelisted — add the keys to
config :logger, :default_formatter, metadata: [...] (or metadata: :all in dev). Passing
user_id: user.id doesn't help if :user_id isn't in that list — it's silently discarded.
Logger Metadata
Set metadata once per request — it's automatically included in all subsequent log calls.
# In a Plug (added to your endpoint or router pipeline)
defmodule MyAppWeb.Plugs.RequestMetadata do
import Plug.Conn
def init(opts), do: opts
def call(conn, _opts) do
Logger.metadata(
request_id: conn.assigns[:request_id] || Ecto.UUID.generate(),
remote_ip: to_string(:inet.ntoa(conn.remote_ip))
)
conn
end
end
# In a LiveView mount
@impl true
def mount(_params, _session, socket) do
if connected?(socket) do
Logger.metadata(user_id: socket.assigns.current_user.id)
end
{:ok, socket}
end
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.
- 5d ago First seen · 404 lines · 32 tokens per session scan A 906babcbe4c4
telemetry-essentials is a skill published in the GitHub repository j-morgan6/elixir-phoenix-guide (159 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,808 once invoked, about $0.0002 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
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…