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.
git 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/rules/jmoak/chrono-mcp/chrono-mcp-standards)<a href="https://agentmods.dev/rules/jmoak/chrono-mcp/chrono-mcp-standards"><img src="https://agentmods.dev/badge/rules/jmoak/chrono-mcp/chrono-mcp-standards/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/rules/jmoak/chrono-mcp/chrono-mcp-standards"><img src="https://agentmods.dev/badge/rules/jmoak/chrono-mcp/chrono-mcp-standards.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.00392 | $0.00392 |
| Opus 5 | $0.00196 | $0.00196 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
chrono-mcp-standards 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 8d 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.
What it actually says
Chrono MCP Project Guidelines
Project Overview
This is a Model Context Protocol (MCP) server for time and date operations, providing tools for:
- Getting current time across timezones
- Time calculations and arithmetic
- Date formatting and conversion
Coding Standards
TypeScript/JavaScript
- Use TypeScript for all new source files
- Prefer functional programming patterns
- Use proper error handling with try-catch blocks
- Export functions and types explicitly
- Follow the existing project structure in
src/directory
MCP Tools
- Each tool should have comprehensive input validation
- Use the existing validation utilities in
src/utils/validation.ts - Follow the MCP protocol standards for tool definitions
- Include proper JSDoc comments for all exported functions
- Provide clear error messages for invalid inputs
Testing
- Write comprehensive tests for all tools using the existing test framework
- Test edge cases and error conditions
- Use descriptive test names that explain the scenario
- Follow the pattern established in existing
.test.tsfiles
Time Handling
- Always use proper timezone-aware date handling
- Leverage the utilities in
src/utils/date-utils.ts - Support ISO 8601 datetime strings as input
- Provide multiple output formats when appropriate
Build Process
- Source files go in
src/directory - Compiled output goes to
dist/directory - Use
npm run buildto compile TypeScript - Use
npm testto run the test suite
Architecture Notes
- The main entry point is
src/index.ts - Tools are organized in
src/tools/directory - Shared utilities are in
src/utils/directory - Each tool exports its definition and implementation
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.
- 8d ago First seen · 53 lines · 392 tokens per session scan A ea77ce620a57
chrono-mcp-standards is a cursor rule published in the GitHub repository JMoak/chrono-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 392 tokens to every session, about $0.0020 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 cursor rules, from other repositories
auth
Auth architecture, middleware chain, and auth-specific coding standards.
tableau-mcp
Tableau MCP project context, architecture overview, and core principles.
tools
MCP tool development patterns — factory pattern, base class, callbacks, and descriptions.
testing
Testing standards — Vitest framework, test organization, mocking patterns.
logging-standards
Use the Operative Control Center logging system instead of print statements.
unreal
Apply this rule for any MCP Tool call for the Unreal Engine editor.