What is chrono-mcp AGENTS.md?

A set of project instructions for the Chrono MCP repository, a TypeScript application that runs on Cloudflare Workers. It documents the folder layout, commands, coding conventions, and tests.

Use it when changing the Chrono parser, types, or Worker entry point, running checks and tests, developing locally, or deploying the application.

Contributors can follow the repository’s existing practices instead of guessing how to build, test, or deploy it. It also explains which tools the project uses, including Bun and Wrangler.

How upamune/chrono-mcp configures Codex and OpenCode

Reuse

Borrowing it

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

Clone the repo

git clone --depth 1 https://github.com/upamune/chrono-mcp

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/upamune/chrono-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/upamune/chrono-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/upamune/chrono-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/upamune/chrono-mcp/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/upamune/chrono-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/upamune/chrono-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 531 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.00531	$0.00531
Opus 5.5	$0.00212	$0.00212
Sonnet 5.5	$0.00106	$0.00106
Haiku 4.5	$0.00053	$0.00053

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

Security

Grade A, and why

chrono-mcp 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 · 30 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

Source TypeScript lives under src/. Chrono logic sits in src/chrono (parser, types, export surface), and the Cloudflare Worker entrypoint is src/worker/handler.ts.
Tests reside in test/ using Bun's runner; mirror the source layout and use descriptive filenames like parser.test.ts.
Configuration files include wrangler.jsonc for Cloudflare routes/bindings, tsconfig*.json for worker/IDE settings, mise.toml for tool versions, and bun.lock to pin dependencies.

Build, Test, and Development Commands

bun install installs dependencies (Bun is the default package manager).
bun run dev delegates to wrangler dev to emulate the Worker locally.
bun run type-check invokes tsc against tsconfig.worker.json without emitting JS; run it before merging schema or type changes.
bun test executes the Bun test suite; bun run test:watch re-runs on file changes.
bun run deploy calls wrangler deploy to publish to Cloudflare Workers; confirm wrangler authentication first.

Coding Style & Naming Conventions

TypeScript targeting ES modules; prefer named exports (parseDateTime, etc.) and central re-exports via src/chrono/index.ts.
Use two-space indentation, trailing semicolons, and double quotes to match the existing codebase.
Keep functions small and composable; add focused JSDoc when logic is not obvious (see helper utilities in parser.ts).
Place shared types in src/chrono/types.ts; name types/interfaces with PascalCase and properties with camelCase.

Testing Guidelines

Add Bun tests under test/ with *.test.ts naming. Group related scenarios with describe blocks.
Cover success paths and error handling (invalid references, timezone offsets, ranges). Include timezone edge cases whenever they are relevant.
Run bun test and bun run type-check before opening a PR; document any skipped tests with justification.

Commit & Pull Request Guidelines

Use Conventional Commits (feat:, fix:, chore:) for clarity until the history dictates otherwise; keep each commit focused.
Pull requests should include a purpose summary, key implementation notes, manual test results, and any Cloudflare configuration updates.
Link issues or tasks where applicable and attach request/response samples or screenshots when they aid review.

Read the full file on GitHub · 30 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 · 30 lines · 531 tokens per session scan A 1a013e00b239

Subscribe to this mod's changes

chrono-mcp AGENTS.md is an instructions file published in the GitHub repository upamune/chrono-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 531 tokens to every session, about $0.0021 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.

chrono-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
chrono-mcp AGENTS.mdupamune/chrono-mcp	Instructions file	1	1y ago	MIT	A	531	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,649	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

chrono-mcp: Instructions file for Codex