What is ChronoGeoLab AGENTS.md?

Repository instructions for ChronoGeoLab, a monorepo for time-based geographic visualization and analysis. A monorepo stores multiple related applications together; here they include a React frontend and a Flask backend connected by an HTTP API.

Use them when changing the frontend or backend, preserving the API boundary, locating project documentation, or working with geospatial data.

They clarify project boundaries and identify which instructions and documentation are authoritative.

How WYZDevin/ChronoGeoLab configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to WYZDevin/ChronoGeoLab. 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/WYZDevin/ChronoGeoLab/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/WYZDevin/ChronoGeoLab

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/wyzdevin/chronogeolab/agents-md/github.svg)](https://agentmods.dev/instructions/wyzdevin/chronogeolab/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/wyzdevin/chronogeolab/agents-md"><img src="https://agentmods.dev/badge/instructions/wyzdevin/chronogeolab/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/wyzdevin/chronogeolab/agents-md"><img src="https://agentmods.dev/badge/instructions/wyzdevin/chronogeolab/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 773 This file is loaded in full into every session.

When invoked 773 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.

Model	Per session	Once invoked
Fable 5.1	$0.00773	$0.00773
Opus 5.5	$0.00309	$0.00309
Sonnet 5.5	$0.00155	$0.00155
Haiku 4.5	$0.00077	$0.00077

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

Security

Grade A, and why

ChronoGeoLab 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 2mo 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 · 63 lines

How it starts

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

AGENTS.md

Instructions for coding agents working on ChronoGeoLab — a monorepo for time-geographic visualization and geospatial analysis. This file is a table of contents: only repo-wide responsibilities and rules live here; details live in the linked docs. Nested AGENTS.md files apply to their directories.

The AGENTS.md files are the source of truth for agent instructions. The CLAUDE.md files only import them; if any other document conflicts, the AGENTS.md file wins. Keep it that way: put new instructions in the linked docs and add a pointer here — do not grow this file into a manual, and do not add per-vendor rule files (.cursorrules, GEMINI.md, .windsurf/, …).

Project Shape

app/front-end/   React + TypeScript + Vite + Redux + deck.gl/maplibre
app/back-end/    Flask + Python 3.12 + GeoPandas/Shapely
docs/            VitePress documentation
demo-datasets/   Sample trajectory data

The frontend and backend are independent applications connected only by the HTTP API.

Rules

Never import code across the frontend/backend boundary.
The API contract (docs/reference/api.md) is the boundary: backend output changes must ripple through the frontend normalizer, TypeScript interfaces, layer accessors/templates, tests, and docs — in the same change.
Keep public API and data-format changes backward compatible unless the task explicitly asks for a breaking change.
Current state (since 2026-06): all analysis tools are temporarily backend_only; the browser implementations remain in place (revert via executionPolicy in stkde-tool.ts / time-geography-tool.ts).
Keep diffs focused on the task; run git status --short first and preserve unrelated user changes. Don't edit generated or vendored files (node_modules/, dist/, docs build output) or lockfiles unless dependencies actually changed. Avoid new dependencies unless justified.
Think before coding; simplicity first; surgical changes; goal-driven execution (full guidelines: .agent/skills/karpathy-guidelines.md).
Validate what you changed (commands in the nested guides); if a check cannot run, say why and state the residual risk.
Update docs when user-facing behavior, setup, data formats, tool options, API responses, or deployment change.

Read the full file on GitHub · 63 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.

2mo ago First seen · 63 lines · 773 tokens per session scan A 01fe75e10db4

Subscribe to this mod's changes

ChronoGeoLab AGENTS.md is an instructions file published in the GitHub repository WYZDevin/ChronoGeoLab (2 stars, last pushed 3mo ago), licensed MIT. It adds 773 tokens to every session, about $0.0031 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-31.

ChronoGeoLab AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ChronoGeoLab AGENTS.mdWYZDevin/ChronoGeoLab	Instructions file	2	3mo ago	MIT	A	773	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

ChronoGeoLab: Instructions file for Codex