bunyan-logging

bunyan-logging is a skill for Claude Code, Codex from openclaw-commons/openclaw-skill-commons. It costs 0 tokens per session (491 once invoked), scanned A, a copy of anyhow-error, MIT.

A command-line skill for using Bunyan, a Node.js logging library that records application events in a structured format.

In plain words
What is it for?
Use it to set up or work with Bunyan-based application logging and choose where output is written.
Why use it?
It gives developers a consistent way to inspect what an application was doing when something goes wrong.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Use it to set up or work with Bunyan-based application logging and choose where output is written.

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

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 bunyan-logging

README.md
[![agentmods](https://agentmods.dev/badge/skills/openclaw-commons/openclaw-skill-commons/bunyan-logging/github.svg)](https://agentmods.dev/skills/openclaw-commons/openclaw-skill-commons/bunyan-logging)
Your own site
<a href="https://agentmods.dev/skills/openclaw-commons/openclaw-skill-commons/bunyan-logging"><img src="https://agentmods.dev/badge/skills/openclaw-commons/openclaw-skill-commons/bunyan-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.

agentmods 80×15 button for bunyan-logging

Your own site · 80×15
<a href="https://agentmods.dev/skills/openclaw-commons/openclaw-skill-commons/bunyan-logging"><img src="https://agentmods.dev/badge/skills/openclaw-commons/openclaw-skill-commons/bunyan-logging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 491 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 78% copy Near-identical to another mod 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.00000 $0.00491
Opus 5 $0.00000 $0.00246
Sonnet 5 $0.00000 $0.00098
Haiku 4.5 $0.00000 $0.00049

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

Security

Grade A, and why

bunyan-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 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.

Origin

This is a copy

78% identical to anyhow-error — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/bunyan-logging/SKILL.md · 83 lines

What it actually says

Bunyan Logging

通用技能

📦 安装

npx clawhub@latest install bunyan-logging

🚀 快速开始

# 使用默认配置
openclaw bunyan-logging

# 查看帮助
openclaw bunyan-logging --help

# 指定配置
openclaw bunyan-logging --config ./config.yaml

📖 功能特性

  • ✅ 完整的Bunyan Logging功能
  • ✅ 开箱即用的默认配置
  • ✅ 详细的文档和示例
  • ✅ 社区支持和持续更新
  • ✅ 与其他技能无缝集成

📝 使用示例

基础用法

openclaw bunyan-logging

高级用法

openclaw bunyan-logging --verbose --output ./output

与其他技能组合

openclaw bunyan-logging | openclaw task-decomposer

⚙️ 配置选项

选项 说明 默认值
--verbose 详细输出模式 false
--output 输出目录 ./output
--config 配置文件路径 ./config.yaml
--help 显示帮助信息 -

📚 相关技能

🤝 贡献

欢迎提交 Issue 和 Pull Request!

📄 许可证

MIT License - 详见 LICENSE


版本: 1.0.0
作者: OpenClaw Community
最后更新: 2026-03-03

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 · 83 lines · 0 tokens per session scan A b9ec71a18e96

Subscribe to this mod's changes

bunyan-logging is a skill published in the GitHub repository openclaw-commons/openclaw-skill-commons (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 491 tokens. A static security scan graded it A with 0 findings. It is 78% identical to anyhow-error, differing in 18 lines, and is treated as a copy.

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