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/loglayer/loglayer-go/agents-mdgit clone --depth 1 https://github.com/loglayer/loglayer-goWhat 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 | $0.05716 | $0.05716 |
| Opus 5 | $0.02858 | $0.02858 |
| Sonnet 5 | $0.01143 | $0.01143 |
| Haiku 4.5 | $0.00572 | $0.00572 |
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 yesterday.
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 — 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
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.
- yesterday First seen · 428 lines · 5,716 tokens per session scan A b52700958233
loglayer-go AGENTS.md is an instructions file published in the GitHub repository loglayer/loglayer-go (5 stars, last pushed 9d ago), licensed MIT. It adds 5,716 tokens to every session, about $0.0286 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-31.
Other instructions, from other repositories
super-speedy-syslog-searcher copilot-instructions.md
Instructions for jtmoon79/super-speedy-syslog-searcher, covering copilot instructions for this repository, code review guidelines, background, directories of note and files of note.
ollama CLAUDE.md
Instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
opensre AGENTS.md
Instructions for Tracer-Cloud/opensre, covering opensre development reference, ci failures and tests (mandatory — every pr / push), build and run commands, code style and tests (high-signal, not exhaustive).
evlog AGENTS.md
Instructions for HugoRCD/evlog, covering evlog, commands, monorepo structure, conventions and code style: no slop.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
gorest AGENTS.md
Instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.