chrono: Instructions file for Codex

AGENTS.md

chrono AGENTS.md is an instructions file for Codex, OpenCode from projectchrono/chrono. It costs 2,011 tokens per session, scanned A, original, BSD-3-Clause.

Repository guidance for Chrono, a C++ physics simulation library built with CMake. It explains the difference between developers and library users, where code belongs, and how to build and test the project.

In plain words
What is it for?
Use it when adding modules, examples, tests, or documentation, or when building and testing Chrono and its optional components.
Why use it?
It helps contributors follow the repository's layout and build rules, including keeping build files outside the source tree.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is projectchrono/chrono's own configuration. It tells Codex and OpenCode how to work on chrono 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 chrono configures →

About the project

Project CHRONO is an open-source C++ library for modeling and simulating physical systems such as connected rigid bodies, deformable bodies, granular materials, fluids, vehicles, and robots. It is used for multiphysics, multibody dynamics, robotics, autonomous-agent, and related engineering simulations.

projectchrono/chrono · 3,140 stars · on GitHub · projectchrono.org

Reuse

Borrowing it

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

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 chrono AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/projectchrono/chrono/agents-md"><img src="https://agentmods.dev/badge/instructions/projectchrono/chrono/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,011 This file is loaded in full into every session.
When invoked 2,011 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 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.1 $0.02011 $0.02011
Opus 5.5 $0.00804 $0.00804
Sonnet 5.5 $0.00402 $0.00402
Haiku 4.5 $0.00201 $0.00201

Measured 1mo ago against content hash 6470157e6c3c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

chrono 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 1mo 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 · 56 lines

How it starts

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

Repository Guidelines

Developers vs. Users

Chrono serves two audiences. Developers modify this repository itself: core libraries, modules, demos, tests, and docs. Users often work in an external repository, build and install Chrono locally, then link against it from their own CMake project. Keep this distinction explicit in your response. Shared guidance below applies to both groups; commit and pull request guidance applies only to developers.

Project Structure & Module Organization

Chrono is a CMake-based C++ project with most production code under src/. Core code lives in src/chrono, optional modules live in sibling directories such as src/chrono_vehicle, src/chrono_sensor, and src/chrono_ros, and examples live in src/demos. C++ unit tests are under src/tests/unit_tests, Python tests under src/tests/unit_tests/python, runtime assets under data/, and API/tutorial docs under doxygen/. Use contrib/ for build helpers, packaging, and Docker files. Keep new code near the owning module and update the local CMakeLists.txt in that directory.

Build, Test, and Development Commands

Chrono forbids in-source builds, so configure into build/ or another separate directory.

  • git submodule init && git submodule update: fetch the bundled third-party sources. There are five, and a missing one surfaces as a confusing configure error: googletest (unit tests), googlebenchmark (benchmark tests), flatbuffers (Chrono::SynChrono), fmu-forge (Chrono::FMI), and SEA-Stack (Chrono::FSI, TDPF solver).
  • cmake -S . -B build -G Ninja -DBUILD_TESTING=ON -DBUILD_DEMOS=ON: configure a local development build.
  • cmake --build build -j: compile the configured targets.
  • ctest --test-dir build --output-on-failure: run the registered CTest suite.
  • cmake --build build --target install: install into the configured prefix.
  • CMakePresets.json carries the CI configurations (linuxci-amd64, linuxci-arm64, macosci, windowsci-vs2022). Use --preset=<name> to reproduce a CI build locally rather than reconstructing its options by hand.

Read the full file on GitHub · 56 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. 1mo ago Changed · -1 tokens per session 6470157e6c3c
  2. 2mo ago Changed · +10 lines · +691 tokens per session 2b6d02da3d1b
  3. 2mo ago First seen · 46 lines · 1,321 tokens per session scan A 48fddffde027

Subscribe to this mod's changes

chrono AGENTS.md is an instructions file published in the GitHub repository projectchrono/chrono (3,140 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 2,011 tokens to every session, about $0.0080 per session on Opus 5.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.

Related

chrono AGENTS.md compared with instructions from other repositories

chrono AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
chrono AGENTS.mdprojectchrono/chronoInstructions file3.1kyesterdayBSD-3-ClauseA2,011Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode