google-calendar-mcp: Instructions file for Codex

AGENTS.md

google-calendar-mcp AGENTS.md is an instructions file for Codex, OpenCode from nspady/google-calendar-mcp. It costs 356 tokens per session, scanned A, original, MIT.

Instructions for an agent that works with Google Calendar accounts. Google Calendar can contain separate calendars such as work and personal, and these rules explain how to choose the right account.

In plain words
What is it for?
Use it when listing calendars or events, or creating events across multiple Google accounts. Specify an account when the request refers to a particular calendar, such as work or personal.
Why use it?
They prevent calendar searches or event changes from using the wrong account. They also explain how operations behave when no account is specified.

Instructions file for CodexOpenCode

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

This is nspady/google-calendar-mcp's own configuration. It tells Codex and OpenCode how to work on google-calendar-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 google-calendar-mcp configures →

About the project

google-calendar-mcp is an MCP server that lets AI assistants connect to Google Calendar and manage calendar information. It supports tasks such as searching, creating, updating, and deleting events, checking availability, handling recurring events, and detecting conflicts across calendars. The catalogue skills, instructions, commands, and agents provide workflows for operating this integration.

nspady/google-calendar-mcp · 1,183 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to nspady/google-calendar-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/nspady/google-calendar-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/nspady/google-calendar-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 google-calendar-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nspady/google-calendar-mcp/agents-md.svg)](https://agentmods.dev/instructions/nspady/google-calendar-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/nspady/google-calendar-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/nspady/google-calendar-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 356 This file is loaded in full into every session.
When invoked 356 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.00356 $0.00356
Opus 5 $0.00178 $0.00178
Sonnet 5 $0.00071 $0.00071
Haiku 4.5 $0.00036 $0.00036

Measured 8d ago against content hash b576ac34f13c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

google-calendar-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 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

AGENTS.md · 49 lines

What it actually says

Agent Guidelines

This document provides instructions for AI agents interacting with the Google Calendar MCP server.

Multi-Account Handling

This server supports connecting to multiple Google accounts simultaneously (e.g., "work", "personal").

Detecting Accounts

You can list available accounts using the list-calendars tool. The tool will return calendars from all connected accounts.

Using the account Parameter

Most tools accept an optional account parameter.

  • If account is OMITTED:

    • Read operations (like list-events) will query all accounts and merge results.
    • Write operations (like create-event) will try to intelligently select the best account based on permissions.
  • If account is SPECIFIED:

    • The operation is restricted to that specific account (or list of accounts).
    • Use this when the user explicitly asks to "check my work calendar" or "add this to my personal schedule".

Example: Listing Events

{
  "name": "list-events",
  "arguments": {
    "timeMin": "2023-10-27T00:00:00Z",
    "account": ["work"]
  }
}

Example: Creating Events

{
  "name": "create-event",
  "arguments": {
    "summary": "Meeting",
    "start": "...",
    "end": "...",
    "account": "work"
  }
}

Calendar Deduplication

The server automatically handles shared calendars. If a calendar is shared between "work" and "personal", it will appear as a single unified calendar in list-calendars. You generally don't need to worry about duplicates.

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. 8d ago First seen · 49 lines · 356 tokens per session scan A b576ac34f13c

Subscribe to this mod's changes

google-calendar-mcp AGENTS.md is an instructions file published in the GitHub repository nspady/google-calendar-mcp (1,183 stars, last pushed 4d ago), licensed MIT. It adds 356 tokens to every session, about $0.0018 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-30.

Related

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens