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 agentmods add instructions/fladdict/vibe-logger/claude-mdgit clone --depth 1 https://github.com/fladdict/vibe-loggerWrote 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/instructions/fladdict/vibe-logger/claude-md)<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="Measured on agentmods" 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.00772 | $0.00772 |
| Opus 5 | $0.00386 | $0.00386 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
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 6d 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 — 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
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.
- 6d ago First seen · 93 lines · 772 tokens per session scan A 72c52d339166
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.0039 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).