cal-scheduler-mcp: Instructions file for Codex

AGENTS.md

cal-scheduler-mcp AGENTS.md is an instructions file for Codex, OpenCode from limey/cal-scheduler-mcp. It costs 2,449 tokens per session, scanned A, original, MIT.

Repository guidance for cal-scheduler, a tool that manages calendar events through CalDAV, a standard used by calendar servers. It covers when the tool fits and how agents should use it.

In plain words
What is it for?
Use it when listing, creating, updating, or deleting calendars and events in one CalDAV account.
Why use it?
It helps agents choose the right calendar tool and handle time zones, recurring events, and single-event changes correctly.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is limey/cal-scheduler-mcp's own configuration. It tells Codex and OpenCode how to work on cal-scheduler-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cal-scheduler-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/limey/cal-scheduler-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/limey/cal-scheduler-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.

agentmods badge for cal-scheduler-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/limey/cal-scheduler-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/limey/cal-scheduler-mcp/agents-md)
Your own site
<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/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.

agentmods 80×15 button for cal-scheduler-mcp AGENTS.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,449 This file is loaded in full into every session.
When invoked 2,449 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02449 $0.02449
Opus 5.5 $0.00980 $0.00980
Sonnet 5.5 $0.00490 $0.00490
Haiku 4.5 $0.00245 $0.00245

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

Security

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 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 · 237 lines

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 .ics store 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 .ics editing). This MCP exposes calendar + scheduling only.
  • The work is not on CalDAV at all (Exchange, Google Calendar API directly, etc.). cal-scheduler is 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

Read the full file on GitHub · 237 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.

  1. 2mo ago First seen · 237 lines · 2,449 tokens per session scan A 777a4655d75d

Subscribe to this mod's changes

cal-scheduler-mcp AGENTS.md is an instructions file published in the GitHub repository limey/cal-scheduler-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 2,449 tokens to every session, about $0.0098 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.

Related

cal-scheduler-mcp AGENTS.md compared with instructions from other repositories

cal-scheduler-mcp AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
cal-scheduler-mcp AGENTS.mdlimey/cal-scheduler-mcpInstructions file14d agoMITA2,449Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode