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.
npx agentmods add instructions/marimerllc/calendar-mcp/copilot-instructionsgit clone --depth 1 https://github.com/MarimerLLC/calendar-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/marimerllc/calendar-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/marimerllc/calendar-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/marimerllc/calendar-mcp/copilot-instructions.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 | $0.01605 | $0.01605 |
| Opus 5 | $0.00803 | $0.00803 |
| Sonnet 5 | $0.00321 | $0.00321 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
calendar-mcp copilot-instructions.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 4d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for Calendar-MCP
This repository contains a Model Context Protocol (MCP) server written in C# / .NET 10 that provides unified access to multiple email and calendar accounts across Microsoft 365, Outlook.com, and Google Workspace.
📖 Quick Context
Read these first when starting work:
- Project Context & Architecture - High-level overview, problem statement, and architecture
- .NET Development Guidelines - .NET best practices and coding standards
- Common Code Patterns - Code patterns and examples for MCP tools, providers, and services
- Build, Test & Environment Setup - How to build, test, and configure the project
- Security Best Practices - Authentication, token management, and security guidelines
- Repository Rules - Documentation and change management rules
Detailed documentation: See /docs folder for comprehensive technical specifications on authentication, providers, routing, security, telemetry, and more.
🎯 Project Overview
This MCP server enables AI assistants (Claude, ChatGPT, GitHub Copilot) to access multiple email and calendar accounts simultaneously. It solves the multi-tenant problem where professionals manage multiple Microsoft 365 tenants, Outlook.com, and Google Workspace accounts.
Key Architecture Points:
- Provider ≠ Account: One provider service manages multiple accounts with isolated credentials
- Per-Account Isolation: Every account has its own authentication context and encrypted token storage
- Smart Routing: Configurable AI backend (Ollama local or cloud APIs) for intelligent account selection
- Security First: Encrypted tokens, minimal privilege scopes, privacy-first telemetry
🏗️ Project Structure
/src # Main source code
/CalendarMcp.Core # Core business logic and services
/CalendarMcp.StdioServer # MCP stdio server implementation
/docs # Comprehensive technical documentation
/spikes # Spike/experimental projects
/.github/instructions # Detailed Copilot instructions
/changelogs # Change logs and summaries (use for documenting 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.
- 4d ago First seen · 156 lines · 1,605 tokens per session scan A 2a49ecdc8083
calendar-mcp copilot-instructions.md is an instructions file published in the GitHub repository MarimerLLC/calendar-mcp (22 stars, last pushed today), licensed MIT. It adds 1,605 tokens to every session, about $0.0080 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.
Other instructions, from other repositories
olkcli CLAUDE.md
Instructions for rlrghb/olkcli, covering claude.md, what is this project?, quick reference, architecture and key patterns.
olkcli AGENTS.md
Instructions for rlrghb/olkcli, covering repository guidelines, project structure, build, test, and development commands, coding style & naming conventions and testing guidelines.
outlook-ews-mcp AGENTS.md
Instructions for viartemev/outlook-ews-mcp, covering agents.md, engineering rules, project shape, testing and conventions.
outlook-ews-mcp CLAUDE.md
Instructions for viartemev/outlook-ews-mcp, a project described as: Secure MCP server for on-prem Microsoft Exchange (EWS) with tools for email, calendar, contacts, folders, attachments, and free/busy availability.
cli AGENTS.md
Instructions for nylas/cli, covering ai coding agent guidelines, quick reference: shared helpers, quick reference: adding a new feature and quick reference: credential storage.
gaia Clean Code.instructions.md
Instructions for theexperiencecompany/gaia: Write clean and minimalistic code. Do not create unnecessary test files, markdown files, or unnecessary files. Prioritize writing clean, modular, and production-level code. Reuse existing logic, paradigms, and abstractions if present. Do not do anything unnecessary or extra.…