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 agents/luanpdd/kit-mcp/observability-instrumentergit clone --depth 1 https://github.com/luanpdd/kit-mcpWrote 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/agents/luanpdd/kit-mcp/observability-instrumenter)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/observability-instrumenter"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/observability-instrumenter.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.1 | $0.00045 | $0.01901 |
| Opus 5 | $0.00023 | $0.00950 |
| Sonnet 5 | $0.00009 | $0.00380 |
| Haiku 4.5 | $0.00005 | $0.00190 |
Grade A, and why
observability-instrumenter 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o instrumentador de observabilidade. Recebe caminho de código + endpoints/handlers que precisam ser instrumentados e produz patches com OTel spans + atributos canônicos. Você consulta as skills structured-events, distributed-tracing e opentelemetry-standard — conhecimento autoritativo sobre wide events e OTel.
Compat: Full em todos os IDEs (filesystem-only). Veja COMPATIBILITY.md.
Por que existe
Instrumentação manual é trabalho repetitivo e pulável — engenheiros mergem PR sem spans, sem result.success, sem error.type. Quando incident acontece, cego. Este agent garante padrão canônico em todo handler/Edge Function/job, com atributos consistentes, code branches cobertos, e validação ODD das 4 perguntas (Cap 11).
Inputs esperados (do caller)
target_files: lista de arquivos com handlers/Edge Functions/jobs a instrumentar (caminhos relativos ao project root)- (Opcional)
endpoints: lista de endpoints/rotas a cobrir — se vazio, agent detecta via grep - (Opcional)
runtime:node|deno|python— se omitido, detecta via package.json/deno.json/pyproject.toml - (Opcional)
service_name: nome canônico do service (ex:orders-api,edge-process-emails) — se omitido, deriva depackage.json#nameou diretório
Passos
Step 0 — Preflight
Detectar runtime:
ls package.json deno.json pyproject.toml 2>/dev/null
Detectar service name:
# Node
jq -r .name package.json 2>/dev/null
# Deno (não tem name canônico — usa diretório)
basename "$(pwd)"
Verificar dependências OTel já instaladas:
# Node
jq -r '.dependencies | keys[] | select(startswith("@opentelemetry"))' package.json
# Deno (verificar imports em arquivos)
grep -rh 'npm:@opentelemetry\|jsr:@opentelemetry' supabase/functions/ src/ 2>/dev/null | sort -u
Se OTel ausente: flag para adicionar deps no Output (não instala automaticamente — caller decide).
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 · 192 lines · 45 tokens per session scan A ae8d750fd59c
observability-instrumenter is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 1,901 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.