agents-evolution: Skill for Claude Code

.agents/skills/logging-helper/SKILL.md

logging-helper is a skill for Claude Code, Codex from kissrosecicd-hub/agents-evolution. It costs 86 tokens per session (1,001 once invoked), scanned A, original, MIT.

A guide to logging in software: recording events, values, errors, state changes, and timings so developers can understand what a program did. It describes useful log levels and a readable, machine-parsable format.

In plain words
What is it for?
Use it when adding logs, tracing a failing operation, investigating edge cases such as empty or missing values, or deciding what to record in production.
Why use it?
It helps developers find bugs and unusual cases from recorded application behaviour instead of guessing after something fails.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is kissrosecicd-hub/agents-evolution's own configuration. It tells Claude Code and Codex how to work on agents-evolution itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agents-evolution configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kissrosecicd-hub/agents-evolution. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kissrosecicd-hub/agents-evolution/main/.agents/skills/logging-helper/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolution

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-helper

README.md
[![agentmods](https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/logging-helper/github.svg)](https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/logging-helper)
Your own site
<a href="https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/logging-helper"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/logging-helper/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-helper

Your own site · 80×15
<a href="https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/logging-helper"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/logging-helper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,001 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.00086 $0.01001
Opus 5 $0.00043 $0.00500
Sonnet 5 $0.00017 $0.00200
Haiku 4.5 $0.00009 $0.00100

Measured 9d ago against content hash 95355bda12dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

logging-helper 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 9d 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.

.agents/skills/logging-helper/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Logging Helper — логирование как инструмент отладки

Контекст

Логи — первый инструмент отладки, не костыль. Логгируй везде: вход/выход функций, ключевые состояния, ошибки, тайминги, неочевидные ветки. Помогают находить баги и edge cases до того, как пользователь заметит.

Стратегия

Что логировать

  • Входные параметры функций (валидация)
  • Возвращаемые значения (особенно при неочевидных результатах)
  • Исключения и стектрейсы
  • Переходы между состояниями
  • Edge cases (пустые массивы, null, boundary values)
  • Тайминги критичных операций (DB queries, API calls, heavy computations)
  • Retry-попытки и fallback-ветки

Уровни логирования

Уровень Когда Пример
error Критичные сбои, требующие вмешательства DB connection lost, API timeout
warn Подозрительное, но система работает Deprecated API, cache miss > 50%
info Ключевые события бизнес-логики User logged in, order created
debug Детальная трассировка для отладки Function entry/exit, intermediate values

Формат

[TIMESTAMP] [LEVEL] [MODULE] message — context: {key: value}
  • Машина-читаемо (парсится локи)
  • Человек-читаемо (понятно без декодера)
  • ISO 8601 для timestamp
  • JSON для context — удобно для grep/jq

Алгоритм отладки через логи

  1. Добавь логи в подозрительные места
  2. Воспроизведи проблему
  3. Проанализируй вывод — найди аномалию
  4. Убери лишнее, оставь ключевые точки контроля
  5. Зафиксируй edge case в тесте

Логирование в продакшене

Логи → Мониторинг → Алерты

  • Не надейся на «проверю руками»
  • Критичные error-логи → алерт (email, Slack, Telegram)
  • Паттерны ошибок → дашборд
  • Ротация логой — не забивай диск

Триггеры

«добавь логи», «логирование», «trace», «отслеживай баг», «edge case», «найди причину», «почему упало», «что тут произошло», «логирование в продакшене»

Примеры

Правильно:

async function processOrder(order: Order) {
  log.debug('[ORDER] processing start', { orderId: order.id, items: order.items.length });
  
  try {
    const result = await validateOrder(order);
    if (!result.valid) {
      log.warn('[ORDER] validation failed', { orderId: order.id, reasons: result.errors });
      return { status: 'rejected', errors: result.errors };
    }
    
    log.info('[ORDER] processed successfully', { orderId: order.id });
    return { status: 'ok' };
  } catch (err) {
    log.error('[ORDER] unexpected error', { orderId: order.id, error: err.message, stack: err.stack });
    throw err;
  }
}

Read the full file on GitHub · 106 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. 9d ago First seen · 106 lines · 0 tokens per session scan A 95355bda12dc

Subscribe to this mod's changes

logging-helper is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 5mo ago), licensed MIT. It adds 86 tokens to every session and 1,001 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-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens