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 eaescob/resiliency_skills --skill logginggit clone --depth 1 https://github.com/eaescob/resiliency_skillsWrote 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/eaescob/resiliency_skills/logging)<a href="https://agentmods.dev/skills/eaescob/resiliency_skills/logging"><img src="https://agentmods.dev/badge/skills/eaescob/resiliency_skills/logging/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/eaescob/resiliency_skills/logging"><img src="https://agentmods.dev/badge/skills/eaescob/resiliency_skills/logging.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.00081 | $0.01063 |
| Opus 5.5 | $0.00032 | $0.00425 |
| Sonnet 5.5 | $0.00016 | $0.00213 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
logging 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 2mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logging
Implement structured logging for debugging, monitoring, and troubleshooting.
Logging Principles
- Structured JSON - Machine-parseable logs for aggregation
- Appropriate levels - DEBUG, INFO, WARN, ERROR
- Context enrichment - Include request ID, user ID, trace ID
- No sensitive data - Never log passwords, tokens, PII
- Actionable messages - Include what happened and context
Log Levels
| Level | When to Use |
|---|---|
| ERROR | Failures requiring immediate attention |
| WARN | Unexpected conditions that don't stop execution |
| INFO | Significant business events (user actions, API calls) |
| DEBUG | Detailed diagnostic info (development only) |
Framework References
Next.js
See references/frameworks/nextjs.md for:
- Server-side logging setup
- API route logging
- Client-side error boundary logging
Express
See references/frameworks/express.md for:
- Winston/Pino configuration
- Request logging middleware
- Error handler logging
Go
See references/frameworks/go.md for:
- slog (standard library) setup
- Structured logging patterns
- Middleware logging
Quick Setup
Node.js with Pino (Recommended)
// lib/logger.ts
import pino from "pino"
export const logger = pino({
level: process.env.LOG_LEVEL || "info",
formatters: {
level: (label) => ({ level: label }),
},
base: {
service: process.env.SERVICE_NAME || "my-service",
env: process.env.NODE_ENV,
},
})
// Usage
logger.info({ userId: user.id, action: "login" }, "User logged in")
logger.error({ err, orderId }, "Failed to process order")
Go with slog
import (
"log/slog"
"os"
)
var logger = slog.New(slog.NewJSONHandler(os.Stdout, &slog.HandlerOptions{
Level: slog.LevelInfo,
}))
// Usage
logger.Info("user logged in", "userId", user.ID, "action", "login")
logger.Error("failed to process order", "error", err, "orderId", orderID)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 170 lines · 81 tokens per session scan A 6804a8199edd
logging is a skill published in the GitHub repository eaescob/resiliency_skills (2 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,063 once invoked, about $0.0003 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…