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/upamune/chrono-mcp/agents-mdgit clone --depth 1 https://github.com/upamune/chrono-mcpWrote 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/upamune/chrono-mcp/agents-md)<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="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 | $0.00531 | $0.00531 |
| Opus 5 | $0.00266 | $0.00266 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
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 4d 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 — 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 insrc/chrono(parser, types, export surface), and the Cloudflare Worker entrypoint issrc/worker/handler.ts. - Tests reside in
test/using Bun's runner; mirror the source layout and use descriptive filenames likeparser.test.ts. - Configuration files include
wrangler.jsoncfor Cloudflare routes/bindings,tsconfig*.jsonfor worker/IDE settings,mise.tomlfor tool versions, andbun.lockto pin dependencies.
Build, Test, and Development Commands
bun installinstalls dependencies (Bun is the default package manager).bun run devdelegates towrangler devto emulate the Worker locally.bun run type-checkinvokestscagainsttsconfig.worker.jsonwithout emitting JS; run it before merging schema or type changes.bun testexecutes the Bun test suite;bun run test:watchre-runs on file changes.bun run deploycallswrangler deployto publish to Cloudflare Workers; confirmwranglerauthentication first.
Coding Style & Naming Conventions
- TypeScript targeting ES modules; prefer named exports (
parseDateTime, etc.) and central re-exports viasrc/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.tsnaming. Group related scenarios withdescribeblocks. - Cover success paths and error handling (invalid references, timezone offsets, ranges). Include timezone edge cases whenever they are relevant.
- Run
bun testandbun run type-checkbefore 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.
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.
- 4d ago First seen · 30 lines · 531 tokens per session scan A 1a013e00b239
chrono-mcp AGENTS.md is an instructions file published in the GitHub repository upamune/chrono-mcp (1 stars, last pushed 11mo ago), licensed MIT. It adds 531 tokens to every session, about $0.0027 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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.