What is log-file-metric-exporter AGENTS.md?

Repository guidance for a Prometheus exporter that watches Kubernetes pod log files and reports how many bytes were logged. Prometheus is a system that collects metrics for monitoring.

Use it when modifying the exporter, its HTTPS and authentication settings, Kubernetes log handling, metrics, or tests.

It gives coding agents the project’s architecture, security rules, and testing expectations in one place, reducing guesswork when changing the exporter.

How ViaQ/log-file-metric-exporter configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to ViaQ/log-file-metric-exporter. 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/ViaQ/log-file-metric-exporter/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/ViaQ/log-file-metric-exporter

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/viaq/log-file-metric-exporter/agents-md/github.svg)](https://agentmods.dev/instructions/viaq/log-file-metric-exporter/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/viaq/log-file-metric-exporter/agents-md"><img src="https://agentmods.dev/badge/instructions/viaq/log-file-metric-exporter/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/viaq/log-file-metric-exporter/agents-md"><img src="https://agentmods.dev/badge/instructions/viaq/log-file-metric-exporter/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,340 This file is loaded in full into every session.

When invoked 2,340 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.02340	$0.02340
Opus 5.5	$0.00936	$0.00936
Sonnet 5.5	$0.00468	$0.00468
Haiku 4.5	$0.00234	$0.00234

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

Security

Grade A, and why

log-file-metric-exporter 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 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.

AGENTS.md · 223 lines

How it starts

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

AGENTS.md

This file provides guidance to automated agents (AI or otherwise) when working with code in this repository.

Project Overview

The log-file-metric-exporter is a Prometheus exporter that monitors Kubernetes pod log files and exports the log_logged_bytes_total counter metric. This allows comparison of bytes actually logged versus what log collectors (e.g., Fluentd, Vector) are able to collect during runtime.

Core Principles

Security First: Default to HTTPS with TLS; authentication should be the norm, not optional
Kubernetes Native: Assume pod log structure at /var/log/pods/<namespace>_<podname>_<uuid>/<container>/
Simplicity: Prefer sequential metric updates and straightforward logic over extreme performance
Testability: All components should have unit tests; benchmarks for performance-critical paths

Architecture Summary

See ARCHITECTURE.md for detailed design decisions, tradeoffs, and implementation details.

Core Components

Main Entry Point (cmd/main.go)
- Parses command-line flags (directory, port, TLS, auth token)
- Sets up HTTPS with TLS certificates and configurable cipher suites
- Mounts Prometheus metrics endpoint with optional bearer token auth
- Spawns LogWatcher in a background goroutine
Log Watcher (pkg/logwatch/watcher.go)
- Watches directory (default: /var/log/pods) for file size changes
- Parses Kubernetes log paths with regex to extract labels: namespace, pod name, pod UUID, container name
- Maintains last-known file sizes; detects growth, truncation, and deletion
- Updates log_logged_bytes_total counter on size changes
- Runs 5 concurrent goroutines to process events
Symlink Notifier (pkg/symnotify/symnotify.go)
- Wraps fsnotify.Watcher to handle Kubernetes symlinked log files
- Auto-adds watches for symlink targets and directories
- Recursively watches subdirectories; re-targets on symlink changes
- Critical for correctness (without this, many events would be missed)

Read the full file on GitHub · 223 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 · 223 lines · 2,340 tokens per session scan A 13b20ea52ca4

Subscribe to this mod's changes

log-file-metric-exporter AGENTS.md is an instructions file published in the GitHub repository ViaQ/log-file-metric-exporter (2 stars, last pushed 10d ago), licensed Apache-2.0. It adds 2,340 tokens to every session, about $0.0094 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.

Analytics and metrics Cloud DevOps and cloud

log-file-metric-exporter AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
log-file-metric-exporter AGENTS.mdViaQ/log-file-metric-exporter	Instructions file	2	10d ago	Apache-2.0	A	2,340	Codex, OpenCode
plan-forge naming.instructions.mdsrnichols/plan-forge	Instructions file	6	2d ago	MIT	A	1,453	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	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	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot

log-file-metric-exporter: Instructions file for Codex