Borrowing it
Nothing to install: this file belongs to JMoak/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.
curl -O https://raw.githubusercontent.com/JMoak/chrono-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/JMoak/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/jmoak/chrono-mcp/agents-md)<a href="https://agentmods.dev/instructions/jmoak/chrono-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/jmoak/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.
<a href="https://agentmods.dev/instructions/jmoak/chrono-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/jmoak/chrono-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01555 | $0.01555 |
| Opus 5.5 | $0.00622 | $0.00622 |
| Sonnet 5.5 | $0.00311 | $0.00311 |
| Haiku 4.5 | $0.00155 | $0.00155 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI coding agents working with code in this repository.
Essential Commands
Build and Development:
npm run build- Compile TypeScript todist/directorynpm run clean- Remove built filesnpm install- Install dependenciesnpm run lint- Run Biome linternpm run lint:fix- Auto-fix linting issues with Biome
Testing and Debugging:
npm test- Vitest unit tests;npm run test:mcp- vibrissa protocol contracts (build first)npm run bench- Vitest benchmarks for batch operations at the MAX_OPERATIONS cap (10k items)npm run inspector- Start MCP Inspector at http://localhost:6274 for interactive testingnode dist/index.js- Run the MCP server directly (requires build first)
Project Architecture
This is a Model Context Protocol (MCP) server that communicates over stdio transport. Key architectural elements:
Core Structure
- Main server:
src/index.tscontains the MCP server setup and tool registration - Modular tools: Each tool should be implemented in its own script under
src/tools/ - Shared utilities: Common date/time utilities in
src/utils/or dedicated date classes - Tool-based architecture: Server exposes tools that clients can call
- Stdio transport: Server communicates via stdin/stdout following MCP protocol
Key Patterns
- Zod validation: All tool parameters use Zod schemas for runtime validation and JSON Schema generation
- Error handling: Uses
McpErrorwith proper error codes for MCP compliance - Tool registration: Two main handlers:
ListToolsRequestSchema- Returns available tools with schemasCallToolRequestSchema- Executes tool calls with validation
Current Implementation
- Server initialized with name/version metadata and tool capabilities
- Example
echotool demonstrates the pattern:- Define Zod schema for parameters
- Register tool in ListTools handler
- Handle execution in CallTool handler with validation
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.
- 1mo ago First seen · 123 lines · 1,555 tokens per session scan A 7dfbf26df2d5
chrono-mcp AGENTS.md is an instructions file published in the GitHub repository JMoak/chrono-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,555 tokens to every session, about $0.0062 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.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.