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/wyzdevin/chronogeolab/agents-mdgit clone --depth 1 https://github.com/WYZDevin/ChronoGeoLabWrote 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/wyzdevin/chronogeolab/agents-md)<a href="https://agentmods.dev/instructions/wyzdevin/chronogeolab/agents-md"><img src="https://agentmods.dev/badge/instructions/wyzdevin/chronogeolab/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.1 | $0.00773 | $0.00773 |
| Opus 5 | $0.00387 | $0.00387 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00077 | $0.00077 |
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 5d 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 — 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 viaexecutionPolicyinstkde-tool.ts/time-geography-tool.ts). - Keep diffs focused on the task; run
git status --shortfirst 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.
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.
- 5d ago First seen · 63 lines · 773 tokens per session scan A 01fe75e10db4
ChronoGeoLab AGENTS.md is an instructions file published in the GitHub repository WYZDevin/ChronoGeoLab (2 stars, last pushed 1mo ago), licensed MIT. It adds 773 tokens to every session, about $0.0039 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-31.
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).
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.
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).
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.
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.
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.