auditar-observabilidade

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

An audit of operational maturity that scores five capabilities and compares the results with an earlier project milestone.

In plain words
What is it for?
Generate an observability maturity report, compare milestones, and use it as a CI check for regressions.
Why use it?
It shows where operational practices have improved or regressed and turns gaps into prioritized actions.

Command for Claude Code

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

Good fit Generate an observability maturity report, compare milestones, and use it as a…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/luanpdd/kit-mcp/auditar-observabilidade
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

README.md
[![agentmods](https://agentmods.dev/badge/commands/luanpdd/kit-mcp/auditar-observabilidade.svg)](https://agentmods.dev/commands/luanpdd/kit-mcp/auditar-observabilidade)
Your own site
<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/auditar-observabilidade"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/auditar-observabilidade.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 861 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.00040 $0.00861
Opus 5 $0.00020 $0.00430
Sonnet 5 $0.00008 $0.00172
Haiku 4.5 $0.00004 $0.00086

Measured 3d ago against content hash 167543a04e41, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

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.md · 104 lines

How it starts

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

Cria/Atualiza:

  • .planning/OMM-REPORT.md — snapshot atual
  • (Em /concluir-marco) .planning/milestones/<v>/OMM-REPORT.md — snapshot arquivado

Após: time tem 5 scores + trend + action items priorizados.

Flags:

  • --previous <marco> — comparar com marco específico (default: detecta automaticamente do MILESTONES.md)
  • --ci — modo CI: exit code 0 se OK, 1 se regression em qualquer capacidade

Quando rodar:

  • Manualmente para snapshot informal
  • Em /auditar-marco (audit pre-conclusion) — Phase 35 INT-FW-04
  • Em /concluir-marco (gate de regression) — Phase 35 INT-FW-05

1. Parsear argumentos

PREVIOUS=$(echo "$ARGUMENTS" | grep -oE -- '--previous [^ ]+' | awk '{print $2}')
CI_MODE=$(echo "$ARGUMENTS" | grep -c -- '--ci' || true)

2. Detectar previous milestone

if [ -z "$PREVIOUS" ]; then
  # PT-BR: extrair último concluído de MILESTONES.md
  PREVIOUS=$(grep -E '^### v[0-9.]+\b' .planning/MILESTONES.md | head -2 | tail -1 | grep -oE 'v[0-9.]+')
fi

3. Dispatch para omm-auditor

Task(
  subagent_type="omm-auditor",
  prompt="
${PREVIOUS:+previous_milestone: ${PREVIOUS}}
mode: ${CI_MODE:+ci}snapshot

Gerar OMM-REPORT.md com:
1. Score 1-5 por capacidade (5 capacidades)
2. Trend vs ${PREVIOUS:-último marco}
3. Action items priorizados P0-P3
4. Regression alerts (se alguma capacidade regrediu)
5. Comparação por marco
"
)

4. Pós-output

═══════════════════════════════════════════════════════════
 framework ► AUDITAR-OBSERVABILIDADE
═══════════════════════════════════════════════════════════

[output do omm-auditor — snapshot inline]

OMM-REPORT.md: .planning/OMM-REPORT.md

${CI_MODE:+## CI Mode}
${CI_MODE:+Exit code: 0 (OK) / 1 (regression detectada)}

Read the full file on GitHub · 104 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. 3d ago First seen · 104 lines · 40 tokens per session scan A 167543a04e41

Subscribe to this mod's changes

auditar-observabilidade is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 861 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-09-03.