Borrowing it
Nothing to install: this file belongs to limey/cal-scheduler-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/limey/cal-scheduler-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/limey/cal-scheduler-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/limey/cal-scheduler-mcp/agents-md)<a href="https://agentmods.dev/instructions/limey/cal-scheduler-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/limey/cal-scheduler-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.1 | $0.02449 | $0.02449 |
| Opus 5 | $0.01224 | $0.01224 |
| Sonnet 5 | $0.00490 | $0.00490 |
| Haiku 4.5 | $0.00245 | $0.00245 |
Grade A, and why
cal-scheduler-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 7d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
You are reading this because you are an agent evaluating
cal-scheduler as a candidate MCP for calendar / scheduling
work. This document is for you. (README.md is for humans.)
What it is
cal-scheduler is a timezone-correct CalDAV scheduling MCP
that exposes a deliberately small surface over the
calendar-and-scheduling slice of CalDAV. It is un-opinionated
about the calendar application itself — it is a layer between
agents and CalDAV, not a calendar app.
When it fits
Pick cal-scheduler when all of the following are true:
- The work is calendar / scheduling (events, recurring series, single-occurrence edits) against a CalDAV account.
- You can express the operation as one of: list / create / update / delete events or calendars, with optional RRULE recurrence, single-occurrence overrides, and mark-done tagging.
- The user has a single CalDAV account and a single timezone they care about (this is by design — see Deliberate reductions below).
- You can tolerate a strict, deterministic server: bad input
fails loudly with a caller-actionable error; the
.icsstore is zoned and RFC-faithful.
When it doesn't
Skip cal-scheduler and look elsewhere when:
- The work is tasks / todos. CalDAV-adjacent functionality is deliberately not exposed. Use a tasks-specific MCP.
- The work needs multi-account or multi-timezone reconciliation. Single account, single timezone is a primary design reduction. Multi-user shared calendars (Google Calendar, iCloud shared, etc.) are out of scope.
- The work needs the full CalDAV surface (freebusy,
scheduling messages, principal properties, raw
.icsediting). This MCP exposes calendar + scheduling only. - The work is not on CalDAV at all (Exchange, Google Calendar
API directly, etc.).
cal-scheduleris CalDAV-only.
Install
The package is on PyPI as cal-scheduler-mcp. The canonical
install is uv tool install:
uv tool install cal-scheduler-mcp
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.
- 7d ago First seen · 237 lines · 2,449 tokens per session scan A 777a4655d75d
cal-scheduler-mcp AGENTS.md is an instructions file published in the GitHub repository limey/cal-scheduler-mcp (1 stars, last pushed today), licensed MIT. It adds 2,449 tokens to every session, about $0.0122 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
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 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.
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).
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.