loglayer-go: Instructions file for Claude Code

AGENTS.md

loglayer-go AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from loglayer/loglayer-go. It costs 5,716 tokens per session, scanned A, original, MIT.

A project guide for LogLayer for Go, a Go library for structured application logs. It describes the library’s layout, design choices, documentation, and ways to check changes.

In plain words
What is it for?
Use it when adding or changing logging features, transports, documentation, or tests in the LogLayer for Go repository.
Why use it?
It helps an agent understand how this Go version relates to the original TypeScript library and where different parts of the codebase belong.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: SessionStart hook event, but also the file is AGENTS.md. Also seen: reads .claude/ paths; mentions Claude Code.

This is loglayer/loglayer-go's own configuration. It tells Claude Code, Codex and OpenCode how to work on loglayer-go 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 loglayer-go configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is replace go.loglayer.dev => ../...

Reuse

Borrowing it

Nothing to install: this file belongs to loglayer/loglayer-go. 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/loglayer/loglayer-go/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/loglayer/loglayer-go

Made for: Claude Code, Codex, OpenCode.

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 loglayer-go AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/loglayer/loglayer-go/agents-md/github.svg)](https://agentmods.dev/instructions/loglayer/loglayer-go/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/loglayer/loglayer-go/agents-md"><img src="https://agentmods.dev/badge/instructions/loglayer/loglayer-go/agents-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.

agentmods 80×15 button for loglayer-go AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/loglayer/loglayer-go/agents-md"><img src="https://agentmods.dev/badge/instructions/loglayer/loglayer-go/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5,716 This file is loaded in full into every session.
When invoked 5,716 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.05716 $0.05716
Opus 5.5 $0.02286 $0.02286
Sonnet 5.5 $0.01143 $0.01143
Haiku 4.5 $0.00572 $0.00572

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

Security

Grade A, and why

loglayer-go AGENTS.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 1mo 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.md · 428 lines

How it starts

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

LogLayer for Go: Agent Guidelines

Note: Always-applicable rules (documentation, code patterns) live in .claude/rules/. This file is high-level project context.

Project Overview

LogLayer for Go is a Go port of the TypeScript loglayer library: a transport-agnostic structured logging library with a fluent API for messages, fields, metadata, and errors.

Module path: go.loglayer.dev GitHub: github.com/loglayer/loglayer-go Docs: VitePress site under docs/

Project Structure

loglayer-go/
├── docs/                       VitePress documentation site
│   ├── .vitepress/             VitePress config (sidebar lives here)
│   └── src/                    Markdown source
│       ├── logging-api/        Per-method API guides
│       ├── transports/         Per-transport guides + _partials/
│       └── ...                 Top-level pages (index, intro, configuration, etc.)
├── transport/                  BaseTransport / BaseConfig / helpers / transporttest
├── transports/                 Built-in transports
│   ├── axiom/                  Wraps github.com/axiomhq/axiom-go
│   ├── blank/                  Delegates to user-supplied function (template for new transports)
│   ├── console/                Plain fmt.Println-style
│   ├── pretty/                 Colorized terminal output (uses fatih/color)
│   ├── structured/             JSON-per-line
│   ├── testing/                In-memory capture for tests
│   ├── zerolog/                Wraps github.com/rs/zerolog
│   ├── zap/                    Wraps go.uber.org/zap
│   ├── phuslu/                 Wraps github.com/phuslu/log (always exits on Fatal)
│   ├── logrus/                 Wraps github.com/sirupsen/logrus
│   └── charmlog/               Wraps github.com/charmbracelet/log
├── loglayer.go                 LogLayer struct + processLog dispatcher
├── builder.go                  LogBuilder fluent chain
├── level.go                    LogLevel + per-level state
├── types.go                    Config, Fields, Data, Metadata aliases
├── fields.go                   WithFields / WithoutFields / mute methods
├── from_context.go             NewContext / FromContext / MustFromContext
├── mock.go                     loglayer.NewMock for silent mocking
└── *_test.go                   Tests + benchmarks

Read the full file on GitHub · 428 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. 1mo ago First seen · 428 lines · 5,716 tokens per session scan A b52700958233

Subscribe to this mod's changes

loglayer-go AGENTS.md is an instructions file published in the GitHub repository loglayer/loglayer-go (5 stars, last pushed 2mo ago), licensed MIT. It adds 5,716 tokens to every session, about $0.0229 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-31.

Related

Other instructions, from other repositories