Borrowing it
Nothing to install: this file belongs to edochi/mdvs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/edochi/mdvs/main/.claude/skills/telemetry/SKILL.mdgit clone --depth 1 https://github.com/edochi/mdvsWrote 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/edochi/mdvs/telemetry)<a href="https://agentmods.dev/skills/edochi/mdvs/telemetry"><img src="https://agentmods.dev/badge/skills/edochi/mdvs/telemetry/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/edochi/mdvs/telemetry"><img src="https://agentmods.dev/badge/skills/edochi/mdvs/telemetry.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.00024 | $0.00688 |
| Opus 5.5 | $0.00010 | $0.00275 |
| Sonnet 5.5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
telemetry 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 10d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Telemetry & Observability Conventions
If the project has a dedicated telemetry/observability spec or conventions document, read it first — it takes precedence over the generic guidance below.
Log Levels
| Level | When to Use | Example |
|---|---|---|
error! |
Unrecoverable failures requiring operator attention | External service call failed permanently |
warn! |
Recoverable issues, degraded operation | Retry triggered, fallback activated |
info! |
Lifecycle events, operational milestones | Server started, connection established |
debug! |
Internal state useful during development | State machine transition details |
trace! |
Per-frame, hot-path data (high volume) | Frame encoded, bytes serialized |
Instrumentation Depth
Not all code deserves the same instrumentation level. Choose based on the crate's role:
- Hot-path code (serialization, framing, tight loops):
trace!only, no spans. Spans add overhead that matters here. - Type definition crates (pure data types, no logic):
trace!only if anything at all. - Core business logic (servers, handlers, state machines): Full
instrumentation —
#[instrument]+ spans. - Client-facing code (SDKs, CLI flows): Full instrumentation for debuggability.
#[instrument] Rules
- Use on async functions that represent logical operations or flow steps
- Skip on hot-path synchronous functions (serialization, encoding, tight loops)
- Always
skipsensitive fields: tokens, keys, passwords, raw payloads - Include identifying fields that aid correlation (IDs, resource names)
- Set appropriate
level— default isINFO, uselevel = "debug"orlevel = "trace"for noisy functions
Structured Logging
Always use named fields, never string interpolation:
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.
- 10d ago First seen · 78 lines · 24 tokens per session scan A 1cf808e9e3b6
telemetry is a skill published in the GitHub repository edochi/mdvs (27 stars, last pushed 11d ago), licensed MIT. It adds 24 tokens to every session and 688 once invoked, about $0.0001 per session on Opus 5.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-10-05.
Other skills, from other repositories
rust-check
Run cargo check on the current Rust project to find compile errors.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
rust-crate-ci
Load before editing any Rust crate in this repo (currently runners/swarm-sandbox-runner). Covers the mandatory local validation gate, common rustfmt/clippy pitfalls, and Windows-specific Rust correctness patterns that CI enforces but are hard to catch locally without a Windows toolchain.
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
pixiv-cli-native
Change or validate pixiv-cli Rust ugoira, cgo/FFI, committed static libraries, vendored dependencies, Linux ABI, and native runner evidence. Use when native sources, library hashes, target toolchains, or encoder behavior change; not for routine Go-only or documentation edits.
codemark
Manage structural code bookmarks that survive refactoring. Use when the user says "remember this", "bookmark this", "save this location", "load my bookmarks", "what do I have bookmarked", "mark this code", "codemark", or when starting a new session and needing to reload context from a previous session. Also use…