when AGENTS.md

Project instructions for the WhenLabs developer toolkit, including its TypeScript setup, testing tools, package manager, monorepo, Docker, and deployment practices. A monorepo is one repository containing multiple related packages.

In plain words
What is it for?
Use them when working on WhenLabs code, especially TypeScript packages, pnpm workspaces, Vitest tests, Docker images, and GitHub Actions workflows.
Why use it?
They give coding agents the project's expected technology choices and conventions, helping changes fit the existing codebase and avoid common Docker or dependency mistakes.

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/whenlabs-org/when/agents-md
Clone the repo
git clone --depth 1 https://github.com/WhenLabs-org/when

Made for: Codex, OpenCode.

Per session 915 This file is loaded in full into every session.
When invoked 915 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.00915 $0.00915
Opus 5 $0.00458 $0.00458
Sonnet 5 $0.00183 $0.00183
Haiku 4.5 $0.00092 $0.00092

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

Security

Grade A, and why

when 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 96 lines

How it starts

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

AGENTS.md

Context

The WhenLabs developer toolkit — 6 tools, one install

Tech Stack

  • Language: TypeScript 5.7
  • Testing: Vitest 3.0
  • Package Manager: pnpm
  • Monorepo: pnpm-workspaces
  • Deployment: Docker
  • CI/CD: GitHub Actions
  • Bundler: tsup 8.0

Conventions

Docker

Dockerfile Best Practices

  • Use multi-stage builds: a builder stage for compilation/dependencies and a slim runner stage for the final image
  • Copy dependency manifests first (package.json, package-lock.json) and install before copying source — leverages layer caching
  • Use specific base image tags (e.g., node:20-alpine) — never use latest in production
  • Run the application as a non-root user: RUN adduser --disabled-password appuser && USER appuser

.dockerignore

  • Always include a .dockerignore file to exclude: node_modules, .git, .env, build artifacts, test files
  • This reduces build context size and prevents secrets from leaking into the image

Layer Caching

  • Order Dockerfile instructions from least to most frequently changing for optimal caching
  • Pin dependency versions in lock files so the install layer is cached until dependencies actually change
  • Use COPY --from=builder to copy only build artifacts into the final stage

Security

  • Never store secrets in the image — use runtime environment variables or secret management
  • Scan images for vulnerabilities: docker scout cves or integrate Trivy/Snyk in CI
  • Keep images minimal — use alpine or distroless base images to reduce attack surface
  • Set HEALTHCHECK instructions for container orchestrators to monitor application health

Compose

  • Use docker-compose.yml for local development with all services (DB, cache, app)
  • Mount source code as a volume for hot-reloading in development
  • Use depends_on with health checks to control startup order

Read the full file on GitHub · 96 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. yesterday First seen · 96 lines · 915 tokens per session scan A a035edf6e659

Subscribe to this mod's changes

when AGENTS.md is an instructions file published in the GitHub repository WhenLabs-org/when (3 stars, last pushed 8d ago), licensed MIT. It adds 915 tokens to every session, about $0.0046 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.