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.
git 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/commands/luanpdd/kit-mcp/observabilidade)<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/observabilidade"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/observabilidade.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.00046 | $0.01373 |
| Opus 5 | $0.00023 | $0.00687 |
| Sonnet 5 | $0.00009 | $0.00275 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
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 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.
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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cria/Atualiza: o que cada agent invocado cria.
Após: o usuário tem o output do agent (patches, SLO.md, snapshot OMM, investigation trail, etc.).
<execution_context>
Skills consultadas pelos agents: kit/skills/_shared-observability/glossary.md (Phase 29) + kit/skills/observability-*/SKILL.md + kit/skills/structured-events/SKILL.md + kit/skills/distributed-tracing/SKILL.md + kit/skills/opentelemetry-standard/SKILL.md + kit/skills/core-analysis-loop/SKILL.md + kit/skills/event-based-slos/SKILL.md + kit/skills/burn-rate-alerting/SKILL.md + kit/skills/telemetry-sampling/SKILL.md + kit/skills/telemetry-pipelines/SKILL.md.
Agents disponíveis: kit/agents/observability-instrumenter.md (Phase 30), kit/agents/incident-investigator.md (Phase 30), kit/agents/slo-engineer.md (Phase 32), kit/agents/burn-rate-forecaster.md (Phase 32), kit/agents/omm-auditor.md (Phase 34).
</execution_context>
Subcomandos suportados (sinônimos PT-BR/EN):
| Subcomando | Sinônimos | Agent dispatched |
|---|---|---|
instrumentar |
instrument, inst |
observability-instrumenter |
investigar |
investigate, incident |
incident-investigator |
slo |
definir-slo, slo-engineer |
slo-engineer |
burn-rate |
burn, burn-rate-forecaster, forecast |
burn-rate-forecaster |
omm |
auditar, audit, maturity |
omm-auditor |
audit-coverage |
cobertura, coverage |
observability-coverage-auditor (v1.12 cross-suite) |
help |
ajuda, ? |
exibe esta tabela inline |
1. Parsear subcomando
SUBCMD=$(echo "$ARGUMENTS" | awk '{print $1}')
ARGS=$(echo "$ARGUMENTS" | cut -d' ' -f2-)
Se $ARGUMENTS for vazio ou SUBCMD for help/ajuda/?: exibir tabela de subcomandos inline + exemplo. Sair.
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 · 119 lines · 46 tokens per session scan A d7fbb6d930da
observabilidade is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,373 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.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.