chronos: Instructions file for Codex

AGENTS.md

chronos AGENTS.md is an instructions file for Codex, OpenCode from sx4im/chronos. It costs 1,449 tokens per session, scanned A, a copy of chronos CLAUDE.md, MIT.

Repository instructions for Chronos, a Node.js and TypeScript framework that tests concurrent systems with controlled time, randomness and networking.

In plain words
What is it for?
They guide coding agents working on deterministic simulation tests and tell them which real-time and random APIs must not be used inside simulations.
Why use it?
They preserve the project’s core rule that simulations must be repeatable, so bugs can be reproduced from the same seed instead of depending on real time or random values.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md; mentions Codex.

This is sx4im/chronos's own configuration. It tells Codex and OpenCode how to work on chronos itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything chronos configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sx4im/chronos. 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/sx4im/chronos/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/sx4im/chronos

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.

agentmods badge for chronos AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sx4im/chronos/agents-md/github.svg)](https://agentmods.dev/instructions/sx4im/chronos/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/sx4im/chronos/agents-md"><img src="https://agentmods.dev/badge/instructions/sx4im/chronos/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.

agentmods 80×15 button for chronos AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sx4im/chronos/agents-md"><img src="https://agentmods.dev/badge/instructions/sx4im/chronos/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,449 This file is loaded in full into every session.
When invoked 1,449 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 95% copy Near-identical to another mod 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.1 $0.01449 $0.01449
Opus 5.5 $0.00580 $0.00580
Sonnet 5.5 $0.00290 $0.00290
Haiku 4.5 $0.00145 $0.00145

Measured 29d ago against content hash 25c1894e9210, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

chronos 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 29d 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

This is a copy

95% identical to chronos CLAUDE.md — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 69 lines

How it starts

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

AGENTS.md — Chronos

This file is read by Codex on every session. It is the project's working memory. Keep it accurate as the project evolves.

What this project is

Chronos is a Deterministic Simulation Testing (DST) framework for Node.js / TypeScript. It runs concurrent/distributed systems on a single controlled thread with virtualized time, seeded randomness, and a simulated network, so any bug — including rare races — reproduces exactly from a single integer seed. It's the FoundationDB/TigerBeetle technique, does not yet exist for JS/TS. (See docs/architecture.md and docs/technical-spec.md.)

THE PRIME DIRECTIVE (never violate)

Determinism is the product. The entire system has exactly one source of entropy (the seeded PRNG) and exactly one source of time (the virtual clock). In any code that runs inside a simulation, you must never use:

  • Date.now(), new Date(), performance.now(), process.hrtime() → use clock.now() / env.now().
  • Math.random() / crypto randomness → use the simulator's Rng / env.random().
  • real setTimeout / setInterval / setImmediate for user timing → use the scheduler / env.sleep / env.setTimeout. (The only allowed real primitive is a single setImmediate used as the microtask-drain barrier in scheduler.ts.)
  • real sockets / fs / network → use the simulated network (env.net).

If the determinism guard test (packages/core/test/determinism.test.ts) ever fails or flakes, stop all other work and fix it first. It is bug class #1.

The core mental model (why DST works here)

V8's execution is already deterministic given identical inputs. Nondeterminism enters Node only through external entropy: wall clock, OS scheduling, network/disk completion order, and Math.random. Chronos removes all external entropy and serializes concurrency onto one thread, so the program replays identically. We do NOT reFibers — we let V8's deterministic microtask draining happen between scheduler steps (via the single setImmediate barrier). Read docs/architecture.md §2.3 before changing scheduler/async code.

Read the full file on GitHub · 69 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. 29d ago First seen · 69 lines · 1,449 tokens per session scan A 25c1894e9210

Subscribe to this mod's changes

chronos AGENTS.md is an instructions file published in the GitHub repository sx4im/chronos (19 stars, last pushed 29d ago), licensed MIT. It adds 1,449 tokens to every session, about $0.0058 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to chronos CLAUDE.md, differing in 4 lines, and is treated as a copy.

Related

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

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens