labrat AGENTS.md

Repository instructions for Codex when maintaining the Labrat project, including its source files, generated lab templates, interfaces, releases, and documentation.

In plain words
What is it for?
Use it when changing Labrat itself, updating its templates or documentation, preparing releases, or checking that Codex and Claude Code interfaces remain aligned.
Why use it?
They give the coding agent clear rules about which files are authoritative and how project changes must stay consistent. They also separate repository maintenance from work inside an individual lab.

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/projectdxai/labrat/agents-md
Clone the repo
git clone --depth 1 https://github.com/ProjectDXAI/labrat

Made for: Codex, OpenCode.

Per session 661 This file is loaded in full into every session.
When invoked 661 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.00661 $0.00661
Opus 5 $0.00331 $0.00331
Sonnet 5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

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

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 45 lines

How it starts

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

labrat repo

This is the repository root, not a runnable lab directory.

Use this file when working on labrat itself from Codex.

If Codex is opened inside a nested lab that has its own AGENTS.md, follow the lab-local file for runtime operation. This root file governs repo maintenance, scaffold consistency, releases, and docs.

Source Of Truth

  • Product/setup docs: README.md, program.md, docs/getting-started.md, docs/runners.md, docs/MODEL_GUIDANCE.md
  • Scaffolded lab UX: templates/AGENTS.md, templates/CLAUDE.md, templates/.agents/skills/, templates/.claude/commands/, templates/agent_prompts/
  • Canonical example lab: examples/nlp-sentiment/research_lab/
  • Packaging/versioning: pyproject.toml, labrat/__init__.py, CHANGELOG.md

Interface Rules

  • Keep Codex and Claude Code first-class. If a lab gets one operator surface, add the matching one for the other interface.
  • Generated labs should ship AGENTS.md, .agents/skills/, CLAUDE.md, .claude/commands/, and agent_prompts/.
  • Keep AGENTS.md short enough to stay durable. Put longer repeatable Codex workflows in .agents/skills/.
  • Do not require a hidden local setup for basic operation. The runnable contract should live in the repo.
  • When operator guidance changes, keep templates, the canonical example lab, and the docs in sync.
  • Prefer labrat ... examples in docs when working from the repo root. Keep the copied scripts/*.py flow valid inside labs.

Frontier Model Rules

  • Use docs/MODEL_GUIDANCE.md for model and prompt-process updates.
  • GPT-5.5 is a Codex host selection, not a lab runtime constant. Do not hardcode API model IDs into labrat for Codex usage.
  • Prefer explicit completion and verification contracts over broad encouragement.
  • Reserve high reasoning effort for design, audit, frame break, profile authoring, and release work.
  • Keep root AGENTS.md focused on repo maintenance; lab runtime details belong in lab-local AGENTS.md and .agents/skills/labrat-operator/SKILL.md.

Read the full file on GitHub · 45 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 · 45 lines · 661 tokens per session scan A e8b73b5c7480

Subscribe to this mod's changes

labrat AGENTS.md is an instructions file published in the GitHub repository ProjectDXAI/labrat (238 stars, last pushed 25d ago), licensed MIT. It adds 661 tokens to every session, about $0.0033 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.