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/experientiallabs/experiential/agents-mdgit clone --depth 1 https://github.com/experientiallabs/experientialWrote 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.
[](https://agentmods.dev/instructions/experientiallabs/experiential/agents-md)<a href="https://agentmods.dev/instructions/experientiallabs/experiential/agents-md"><img src="https://agentmods.dev/badge/instructions/experientiallabs/experiential/agents-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.05666 | $0.05666 |
| Opus 5 | $0.02833 | $0.02833 |
| Sonnet 5 | $0.01133 | $0.01133 |
| Haiku 4.5 | $0.00567 | $0.00567 |
Grade A, and why
experiential 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent guide — experiential
Experiential builds immutable task evidence from agent traces, composes and fits frozen model routers,
runs those routers on loopback, and executes bounded SFT from persisted datasets. All importable
code lives under exp/; benchmark data arrives as a dependency (see rule 6).
Toolchain
Managed with uv; lint/format with ruff; type-check with ty.
uv sync --extra dev
uv run ruff check .
uv run ruff format --check .
uv run ty check
uv run pytest -q
Repository checks
- Every new or rewritten hand-authored source, configuration, and documentation file with a
covered suffix stays below 1,000 physical lines. The executable limit is 999 lines and counts
comments and blank lines. Test modules named
*_test.pyare exempt so cohesive tests are not split solely to satisfy a line count. Generated lock files are excluded. Generated code belongs in an explicitly namedgenerated/directory and is never edited by hand. - Full-repository Ruff check, Ruff format check, and ty check are required on every change. No pre-existing lint or type failures are grandfathered.
- Production imports follow the approved dependency direction: common may not import runtime, simulation, optimize, or cli; runtime may not import simulation, optimize, or cli; simulation may not import optimize or cli; optimize may not import cli. Optimize owns application orchestration and may depend inward on common, runtime, and simulation. The AST gate rejects every current forbidden edge directly and proves that the package graph is acyclic.
- The root CLI command set is exact:
build,config,optimize, andrun. An invocation without a subcommand opens the default gateway home screen.exp/cli/app_test.pyand the release tests enforce the current command and distribution shape.
CLI package ownership
exp/cli/app.pyowns root command composition only. Command implementations live in thebuild/,config/,judge/,optimize/, andgateway/packages. Gateway serving and the default home screen live undergateway/.exp/cli/providers/owns provider discovery, model selection, and catalog setup shared by commands. Command-specific orchestration stays with its command package. In particular, router-candidate collection belongs toexp/cli/optimize/.exp/cli/shared/owns reusable terminal, Typer, consent, picker, and progress primitives. It must not import command packages.exp/cli/providers/may importshared/, but it must not import command packages.- Keep the
exp/cli/root closed to new command implementation modules. Package-wide CLI tests may live inexp/cli/tests/; module tests stay beside the module they cover.
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.
- 3d ago First seen · 355 lines · 5,666 tokens per session scan A 1527a15aa911
experiential AGENTS.md is an instructions file published in the GitHub repository experientiallabs/experiential (754 stars, last pushed 3d ago), licensed Apache-2.0. It adds 5,666 tokens to every session, about $0.0283 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.