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 skills add parisgroup-ai/imersao-ia-setup --skill logger-designgit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/skills/parisgroup-ai/imersao-ia-setup/logger-design)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/logger-design"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/logger-design/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.
<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/logger-design"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/logger-design.svg" alt="Reviewed on agentmods" width="80" 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.00073 | $0.06711 |
| Opus 5 | $0.00036 | $0.03356 |
| Sonnet 5 | $0.00015 | $0.01342 |
| Haiku 4.5 | $0.00007 | $0.00671 |
Grade A, and why
logger-design 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 12d 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 — 959 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logger Design Skill
Esta skill define padrões rígidos para logging estruturado com distributed tracing, garantindo rastreabilidade completa e segurança de dados sensíveis.
Core Principle
Logs são a memória do sistema. Estruturados, rastreáveis e seguros.
┌─────────────────────────────────────────────────────────────┐
│ ESTRUTURADO: Schema rígido, campos obrigatórios │
│ RASTREÁVEL: Distributed tracing com correlation IDs │
│ SEGURO: PII sanitizado, dados sensíveis protegidos │
└─────────────────────────────────────────────────────────────┘
Schema de Log Obrigatório
Interface Base
interface LogEntry {
// === OBRIGATÓRIOS ===
timestamp: string; // ISO 8601: "2024-01-15T10:30:00.000Z"
level: LogLevel; // "debug" | "info" | "warn" | "error" | "fatal"
message: string; // Descrição legível
service: string; // Nome do serviço/app
environment: string; // "development" | "staging" | "production"
// === TRACING (obrigatório em requests) ===
traceId: string; // ID único da requisição raiz
spanId: string; // ID do span atual
parentSpanId?: string; // ID do span pai (se existir)
// === CONTEXTO (quando disponível) ===
userId?: string; // ID do usuário (nunca PII direto)
sessionId?: string; // ID da sessão
requestId?: string; // ID da requisição HTTP
// === TÉCNICO ===
caller?: string; // "file.ts:123:functionName"
duration?: number; // Duração em ms (para operações)
// === DADOS ADICIONAIS ===
data?: Record<string, unknown>; // Contexto específico
error?: ErrorInfo; // Detalhes do erro (se level = error/fatal)
}
interface ErrorInfo {
name: string;
message: string;
stack?: string;
code?: string;
cause?: ErrorInfo;
}
type LogLevel = 'debug' | 'info' | 'warn' | 'error' | 'fatal';
Níveis de Log
| Nível | Quando usar | Exemplo | Produção |
|---|---|---|---|
debug |
Desenvolvimento, troubleshooting | "Query params: {...}" | ❌ Off |
info |
Eventos normais de negócio | "Order created" | ✅ On |
warn |
Situação inesperada, não crítica | "Retry attempt 2/3" | ✅ On |
error |
Erro que afeta operação | "Payment failed" | ✅ On |
fatal |
Sistema comprometido | "Database connection lost" | ✅ On |
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.
- 12d ago First seen · 959 lines · 73 tokens per session scan A 2250bdcf0135
logger-design is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 6,711 once invoked, about $0.0004 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 skills, from other repositories
monitoring-observability
Monitoring and observability patterns for Prometheus metrics, Grafana dashboards, Langfuse v4 LLM tracing (astype, scorecurrentspan, shouldexportspan, LangfuseMedia), and drift detection. Use when adding logging, metrics, distributed tracing, LLM cost tracking, or quality drift monitoring.
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
golang-observability-opentelemetry
Instrumenting Go applications with OpenTelemetry for distributed tracing, Prometheus for metrics, and structured logging with slog.
datadog
Full-stack observability with Datadog APM, logs, metrics, synthetics, and RUM. Use when implementing monitoring, tracing, alerting, or cost optimization for production systems.
Observability Checklist
Reviews a service or codebase against a full observability checklist — logs, metrics, traces, and alerting gaps.
Logging and Observability Guard
Ensure code changes keep logs/metrics/traces useful for debugging failures and regressions.