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/adrielp/ai-engineering-harness/validate_telemetrynpx skills add adrielp/ai-engineering-harness --skill validate_telemetrygit clone --depth 1 https://github.com/adrielp/ai-engineering-harnessWrote 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/adrielp/ai-engineering-harness/validate_telemetry)<a href="https://agentmods.dev/skills/adrielp/ai-engineering-harness/validate_telemetry"><img src="https://agentmods.dev/badge/skills/adrielp/ai-engineering-harness/validate_telemetry.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.00042 | $0.00338 |
| Opus 5 | $0.00021 | $0.00169 |
| Sonnet 5 | $0.00008 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
validate_telemetry scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. The local Aspire dashboard is reachable (`curl -sf http://localhost:18888` What it actually says
Validate Telemetry
Activate the observability-driven-development skill and run its Validation section.
Mode Detection
- If an argument was provided and it resolves to an existing file under
thoughts/shared/telemetry/, run Mode A — Spec-Driven Validation. - Otherwise (no argument, or argument doesn't resolve), run Mode B — Generic Health Check.
Pre-Flight
Before running either mode, confirm:
- The local Aspire dashboard is reachable (
curl -sf http://localhost:18888returns 2xx). - The user's service is configured to export to the dashboard
(
OTEL_EXPORTER_OTLP_ENDPOINTset).
If either fails, surface a one-line setup hint pointing at
observability-driven-development/local-setup.md and stop.
Output
Per the report format in the ODD skill's Validation section. Don't modify code or config silently — the report is the output.
Relationship to Other Commands
Ticket → /create_plan → [ODD: write narrative]
→ /implement_plan → /validate_plan (correctness)
→ /validate_telemetry (telemetry) → /commit
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.
- 4d ago First seen · 48 lines · 42 tokens per session scan A bc52936d0fe4
validate_telemetry is a skill published in the GitHub repository adrielp/ai-engineering-harness (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 338 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…