What is vibe-logger CLAUDE.md?

Repository instructions for Vibe Coding Logger, a Python logging tool designed to give AI coding agents structured debugging context. It records information such as arguments, stack traces, environment details and links between related operations in JSON logs.

Use them when developing or integrating the logger, handling structured debugging data, adding annotations or maintaining its thread safety, memory limits and log rotation.

Ordinary logs may omit the context an AI agent needs to understand a failure. These instructions define a logging approach that preserves richer, machine-readable information while fitting Python's logging system.

How fladdict/vibe-logger configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to fladdict/vibe-logger. 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/fladdict/vibe-logger/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/fladdict/vibe-logger

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/fladdict/vibe-logger/claude-md/github.svg)](https://agentmods.dev/instructions/fladdict/vibe-logger/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/fladdict/vibe-logger/claude-md"><img src="https://agentmods.dev/badge/instructions/fladdict/vibe-logger/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/fladdict/vibe-logger/claude-md"><img src="https://agentmods.dev/badge/instructions/fladdict/vibe-logger/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 772 This file is loaded in full into every session.

When invoked 772 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00772	$0.00772
Opus 5.5	$0.00309	$0.00309
Sonnet 5.5	$0.00154	$0.00154
Haiku 4.5	$0.00077	$0.00077

Measured 2mo ago against content hash 72c52d339166, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vibe-logger CLAUDE.md 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.

CLAUDE.md · 93 lines

How it starts

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

VIBE LOGGER PROJECT

🎯 Goal

Build an AI-native logger specifically designed for VibeCoding - a development paradigm where AI agents are the primary code creators and need rich, structured context to understand and debug effectively.

🌟 Core Concept

In agent-based coding with language models, the critical challenge is maximizing the contextual information passed to coding LLMs. VibeCoding Logger addresses this by creating "AI briefing packages" rather than traditional human-readable logs.

🏗️ Architecture Principles

AI-First Design

Structured JSON format optimized for LLM parsing
Rich context capture including function arguments, stack traces, and environment
Correlation tracking to link related operations across the codebase
Human annotations embedded directly in logs for AI instructions

Technical Excellence

Thread-safe implementation with proper locking mechanisms
Memory-efficient with configurable limits and automatic rotation
Standards-compliant integration with Python's logging ecosystem
Production-ready with comprehensive test coverage

🛠️ Technology Stack

Current Implementation

Python 3.7+ with type hints
JSON Lines format for efficient log storage
Threading locks for concurrent safety
Standard logging integration via handlers and adapters

Future Expansions

TypeScript/Node.js implementation (planned)
Go implementation (future)
Rust implementation (future)
Cross-language correlation support

📋 Development Guidelines

Code Quality Standards

Loose coupling between components
Standard patterns and idiomatic code
AI-readable code with clear structure and naming
Comprehensive docstrings for LLM understanding

Testing Philosophy

Test-driven development for critical features
Edge case coverage including unicode, threading, and errors
Integration testing with real-world scenarios
Performance benchmarks for high-load situations

Read the full file on GitHub · 93 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.

2mo ago First seen · 93 lines · 772 tokens per session scan A 72c52d339166

Subscribe to this mod's changes

vibe-logger CLAUDE.md is an instructions file published in the GitHub repository fladdict/vibe-logger (143 stars, last pushed 1y ago), licensed MIT. It adds 772 tokens to every session, about $0.0031 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-30.

Debugging

vibe-logger CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
vibe-logger CLAUDE.mdfladdict/vibe-logger	Instructions file	143	1y ago	MIT	A	772	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

vibe-logger: Instructions file for Claude Code