auditar-observabilidade-cobertura

auditar-observabilidade-cobertura is a command for Claude Code from luanpdd/kit-mcp. It costs 57 tokens per session (2,019 once invoked), scanned A, original, MIT.

An observability audit command for Supabase projects that counts Edge Functions with key signals, service-level objectives, burn-rate alerts, and characterization tests.

In plain words
What is it for?
Use it to create a scored coverage report and prioritize work on the most-used Edge Functions.
Why use it?
It shows how much monitoring and test coverage is missing and ranks the most important gaps by recent traffic.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Good fit Use it to create a scored coverage report and prioritize work on the most-used Edge Functions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/luanpdd/kit-mcp/auditar-observabilidade-cobertura
Install

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.

Clone the repo
git clone --depth 1 https://github.com/luanpdd/kit-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for auditar-observabilidade-cobertura

README.md
[![agentmods](https://agentmods.dev/badge/commands/luanpdd/kit-mcp/auditar-observabilidade-cobertura/github.svg)](https://agentmods.dev/commands/luanpdd/kit-mcp/auditar-observabilidade-cobertura)
Your own site
<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/auditar-observabilidade-cobertura"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/auditar-observabilidade-cobertura/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.

agentmods 80×15 button for auditar-observabilidade-cobertura

Your own site · 80×15
<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/auditar-observabilidade-cobertura"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/auditar-observabilidade-cobertura.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,019 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.02019
Opus 5 $0.00028 $0.01009
Sonnet 5 $0.00011 $0.00404
Haiku 4.5 $0.00006 $0.00202

Measured 7d ago against content hash b77185017145, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

auditar-observabilidade-cobertura 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 7d 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.

kit/commands/auditar-observabilidade-cobertura.md · 184 lines

How it starts

The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.

  • Edge functions emitindo 4 golden signals: X / N
  • Edge functions com SLO definido: Y / N
  • Edge functions com burn rate alert: Z / N
  • Edge functions com characterization tests: W / N
  • Top 5 funções mais críticas (por chamadas 30d) sem cobertura completa

Invoca o agente observability-coverage-auditor que cross-references skills v1.9 + v1.10 + v1.12.

Cria/Atualiza:

  • .planning/OBSERVABILITY-COVERAGE.md — relatório scored com tabela X/N por dimensão + top críticas + recomendações priorizadas

Após: o user vê tamanho do buraco quantitativamente e tem fila ordenada por (traffic × missing dimensions). As 2 que ele instrumentou às pressas viram baseline; as outras N entram na fila ordenada.

Exemplos:

/auditar-observabilidade-cobertura                                    # defaults
/auditar-observabilidade-cobertura --top-n 10                         # listar top 10
/auditar-observabilidade-cobertura --dimensions signals,slo           # só 2 dimensões
/auditar-observabilidade-cobertura --traffic-window 7d                # janela menor

Pré-requisitos:

  • Projeto Supabase (supabase/config.toml presente)
  • MCP Supabase conectado para traffic data + Edge Functions list (recomendado)
  • Sem MCP: agent reverte para enumerate via filesystem (sem traffic data → top-N por filesystem only)

Quando este comando é o caminho:

  • Você quer "ver o buraco" antes de priorizar instrumentação
  • Você instrumentou algumas Edge Functions ad-hoc; agora quer audit estruturado das outras
  • Audit trimestral cross-suite
  • Pré-requisito de /concluir-marco quando workflow.observability_coverage_threshold opt-in
  • /auditar-marco chain (audit milestone consume este)

1. Parsear argumentos

TRAFFIC_WINDOW=$(echo "$ARGUMENTS" | grep -oE -- '--traffic-window [^ ]+' | awk '{print $2}')
TOP_N=$(echo "$ARGUMENTS" | grep -oE -- '--top-n [0-9]+' | awk '{print $2}')
DIMENSIONS=$(echo "$ARGUMENTS" | grep -oE -- '--dimensions [^ ]+' | awk '{print $2}')
OUTPUT_PATH=$(echo "$ARGUMENTS" | grep -oE -- '--output [^ ]+' | awk '{print $2}')

[ -z "$TRAFFIC_WINDOW" ] && TRAFFIC_WINDOW="30d"
[ -z "$TOP_N" ]          && TOP_N=5
[ -z "$DIMENSIONS" ]     && DIMENSIONS="signals,slo,burn-alert,characterization"
[ -z "$OUTPUT_PATH" ]    && OUTPUT_PATH=".planning/OBSERVABILITY-COVERAGE.md"

mkdir -p "$(dirname "$OUTPUT_PATH")"

Read the full file on GitHub · 184 lines

Changes

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.

  1. 7d ago First seen · 184 lines · 57 tokens per session scan A b77185017145

Subscribe to this mod's changes

auditar-observabilidade-cobertura is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 2,019 once invoked, about $0.0003 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-09-03.