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 commands/adrielp/ai-engineering-harness/validate_telemetrygit clone --depth 1 https://github.com/adrielp/ai-engineering-harnessWhat 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.00000 | $0.00255 |
| Opus 5 | $0.00000 | $0.00128 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
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 3d 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.
- 3d ago First seen · 37 lines · 0 tokens per session scan A b3c698454495
validate_telemetry is a command published in the GitHub repository adrielp/ai-engineering-harness (20 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 255 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.