evlog AGENTS.md

Repository instructions for evlog, a TypeScript logging library in a pnpm monorepo, which is a repository containing multiple related packages or applications. They document project commands and conventions.

In plain words
What is it for?
Use them when developing, testing, linting, type-checking, building, or documenting evlog. They also cover the playground, documentation site, telemetry dashboard, command-line tools, and sandbox applications.
Why use it?
They give coding assistants the project structure, required setup steps, and correct commands before making changes. This helps avoid using the wrong package or skipping generated files.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/hugorcd/evlog/agents-md
Clone the repo
git clone --depth 1 https://github.com/HugoRCD/evlog

Made for: Codex, OpenCode.

Per session 4,053 This file is loaded in full into every session.
When invoked 4,053 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.04053 $0.04053
Opus 5 $0.02027 $0.02027
Sonnet 5 $0.00811 $0.00811
Haiku 4.5 $0.00405 $0.00405

Measured 2d ago against content hash aaeeb1c99c4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

evlog 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 2d 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 · 201 lines

How it starts

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

evlog

TypeScript logging library focused on wide events and structured error handling. pnpm monorepo (managed with Corepack).

Commands

pnpm install                       # install deps
pnpm run dev:prepare               # generate types (required before lint/typecheck after a fresh install)
pnpm run dev                       # start playground
pnpm run build:package             # build the package
pnpm run test                      # run tests (vitest)
pnpm run lint                      # lint all packages
pnpm run typecheck                 # type-check all packages
pnpm run docs                      # start docs site
pnpm run telemetry                 # start the telemetry dashboard (apps/telemetry)
pnpm telemetry:cli <command>       # run this repo's CLI into that local dashboard (--cwd to target an app)
pnpm cli:sandbox                   # disposable per-framework apps under .sandbox/ to test the CLI by hand (--reset restores them, --smoke runs the feature matrix)
pnpm content:lint [path]           # rank the written corpus by content findings (see scripts/content-lint/README.md)
pnpm content:lint:test             # the scanner's own tests, including its two calibration fixtures

Publishing is automated: changesets + .github/workflows/release.yml. Never run pnpm release or changeset publish manually.

Use corepack enable once so the packageManager field in package.json pins the right pnpm version automatically.

After a clean pnpm install, run pnpm run dev:prepare before pnpm run lint / typecheck. Packages like @evlog/nuxthub extend generated .nuxt/tsconfig.json files; without prepare, turbo lint fails on missing extends.

Monorepo Structure

packages/evlog/            Main package
  src/nuxt/                Nuxt module
  src/nitro/, src/nitro-v3/  Nitro plugin (v2 + v3)
  src/vite/                Vite plugin (evlog/vite)
  src/shared/              Toolkit — exposed as evlog/toolkit (NOT evlog/shared)
  src/ai/                  AI SDK integration (evlog/ai)
  src/adapters/            Drain adapters (Axiom, OTLP, HyperDX, PostHog, Sentry, Better Stack, Datadog, Loki, ClickHouse, fs, memory)
  src/enrichers/           Built-in enrichers (UserAgent, Geo, RequestSize, TraceContext)
  src/runtime/             Runtime code (client/, server/, utils/)
  src/<framework>/         One dir per framework integration (hono/, next/, sveltekit/, nestjs/, express/, fastify/, elysia/, orpc/, react-router/, workers/, eve/, better-auth/)
  test/                    Tests
packages/cli/              @evlog/cli — log exploration CLI (`pnpm cli`)
packages/nuxthub/          @evlog/nuxthub
packages/telemetry/        @evlog/telemetry
apps/playground/           Main dev environment (`pnpm dev`)
apps/docs/                 Docus documentation site — has its own AGENTS.md
apps/*                     Framework playgrounds (next, nitro, nitro-v2, nuxthub, lab, telemetry, ...) — `pnpm playground` to pick one
examples/                  ~22 runnable examples, one per framework — includes the community-*-skeleton dirs used by the create-adapter/enricher/framework skills
scripts/                   Repo tooling (run-app, cli-sandbox, release-notes, content-lint)
.agents/skills/            Internal skills for creating adapters, enrichers, and framework integrations, and for writing content — each carries `metadata: internal: true` in its frontmatter so the skills CLI skips them for public installs
skills/                     Published skills (analyze-logs, build-audit-logs, review-logging-patterns) — served by the docs site via `/.well-known/skills/` and discovered by `npx skills add hugorcd/evlog`

Read the full file on GitHub · 201 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. 2d ago First seen · 201 lines · 4,053 tokens per session scan A aaeeb1c99c4e

Subscribe to this mod's changes

evlog AGENTS.md is an instructions file published in the GitHub repository HugoRCD/evlog (1,831 stars, last pushed today), licensed MIT. It adds 4,053 tokens to every session, about $0.0203 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.