logger-design

logger-design is a skill for Claude Code from parisgroup-ai/imersao-ia-setup. It costs 73 tokens per session (6,711 once invoked), scanned A, original, MIT.

A set of rules for writing structured logs and tracking requests across multiple services. It covers Node.js, Python, Go, and frontend code, including request IDs and removal of personal data.

In plain words
What is it for?
Use it when adding or reviewing logging, distributed tracing, correlation IDs, spans, or observability in an application.
Why use it?
It helps make logs consistent, traceable, and safer to store. That reduces the effort needed to follow a request through different parts of an application and avoids exposing sensitive information.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the imersao plugin — 51 skills, 7 commands shipped together

Good fit Use it when adding or reviewing logging, distributed tracing, correlation IDs, spans, or observability in an application.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/parisgroup-ai/imersao-ia-setup/logger-design
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.

Any agent
npx skills add parisgroup-ai/imersao-ia-setup --skill logger-design
Clone the repo
git clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setup

Made for: Claude Code.

Or install imersao, the plugin that ships this one along with the rest of its 51 skills, 7 commands.

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 logger-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/logger-design/github.svg)](https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/logger-design)
Your own site
<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.

agentmods 80×15 button for logger-design

Your own site · 80×15
<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>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,711 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.00073 $0.06711
Opus 5 $0.00036 $0.03356
Sonnet 5 $0.00015 $0.01342
Haiku 4.5 $0.00007 $0.00671

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

Security

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.

plugins/imersao/skills/logger-design/SKILL.md · 959 lines

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

Read the full file on GitHub · 959 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. 12d ago First seen · 959 lines · 73 tokens per session scan A 2250bdcf0135

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories