logging-best-practices

logging-best-practices is a skill for Claude Code, Codex from ncklrs/startup-os-skills. It costs 60 tokens per session (603 once invoked), scanned A, original, no licence file.

A guide to writing useful application logs, which are records that help developers understand what software is doing.

In plain words
What is it for?
Use it when adding or reviewing logs, debugging production issues, and deciding which event details, fields, or samples to record.
Why use it?
It helps avoid noisy or unhelpful logs and supports investigating problems in live systems.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it when adding or reviewing logs, debugging production issues, and deciding which event details, fields, or samples to record.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ncklrs/startup-os-skills/logging-best-practices
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 ncklrs/startup-os-skills --skill logging-best-practices
Clone the repo
git clone --depth 1 https://github.com/ncklrs/startup-os-skills

Made for: Claude Code, Codex.

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 logging-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/ncklrs/startup-os-skills/logging-best-practices/github.svg)](https://agentmods.dev/skills/ncklrs/startup-os-skills/logging-best-practices)
Your own site
<a href="https://agentmods.dev/skills/ncklrs/startup-os-skills/logging-best-practices"><img src="https://agentmods.dev/badge/skills/ncklrs/startup-os-skills/logging-best-practices/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 logging-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/ncklrs/startup-os-skills/logging-best-practices"><img src="https://agentmods.dev/badge/skills/ncklrs/startup-os-skills/logging-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 603 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 unknown 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.00060 $0.00603
Opus 5 $0.00030 $0.00302
Sonnet 5 $0.00012 $0.00121
Haiku 4.5 $0.00006 $0.00060

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

Security

Grade A, and why

logging-best-practices 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.

skills/logging-best-practices/SKILL.md · 75 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 75 lines · 60 tokens per session scan A bdeef0488ba2

Subscribe to this mod's changes

logging-best-practices is a skill published in the GitHub repository ncklrs/startup-os-skills (50 stars, last pushed 6mo ago), with no licence file. It adds 60 tokens to every session and 603 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

langsmith-fetch

Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires…

OthmanAdi/langsmith-fetch-skill · 59 tokens

python-lsp

Semantic Python code queries via a stdio LSP client driving pyright-langserver. Provides binding-resolved go-to-definition, find-references, hover types, type diagnostics, file symbol outlines, and project-wide symbol search — name resolution and type inference that tree-sitter and ripgrep cannot do. Use when you need…

oaustegard/claude-skills · 155 tokens

searching-codebases

Binding-resolved Python symbol queries via pyright — every true caller (--refs), the real definition (--def), or an inferred signature (--hover) of a .py symbol, excluding the same-named false positives text search cannot tell apart. Use when a task needs ALL callers or users of a named Python symbol and grep would…

oaustegard/claude-skills · 133 tokens

check-tools

Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies.

oaustegard/claude-skills · 37 tokens

technical-debt-audit

Use when the user says 'clean up my wordpress', 'what is bloating my wordpress', 'find orphaned shortcodes', or 'scan for unused plugins'. Audits orphaned shortcodes from deleted plugins, unused plugins, database bloat, unused media, and leftover data from inactive builders.

respira-press/agent-skills-wordpress · 66 tokens

wordpress-site-dna

Use when the user says 'analyze my wordpress site', 'what is running on my site', 'site dna', or 'what plugins are on my site'. Detects every page builder, audits active versus dead-weight plugins, maps content structure, finds orphaned shortcodes, and checks performance and security posture.

respira-press/agent-skills-wordpress · 68 tokens