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/peadams21/google-calendar-mcp-server/copilot-instructionsgit clone --depth 1 https://github.com/peadams21/Google-Calendar-MCP-ServerWrote 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/peadams21/google-calendar-mcp-server/copilot-instructions)<a href="https://agentmods.dev/instructions/peadams21/google-calendar-mcp-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/peadams21/google-calendar-mcp-server/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.1 | $0.00373 | $0.00373 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade C, and why
Google-Calendar-MCP-Server copilot-instructions.md scanned grade C with 1 finding 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 5d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Use this file to provide workspace-specific custom instructions to Copilot. For more details, visit https://code.visualstudio.com/docs/copilot/copilot-customization#_use-a-githubcopilotinstructionsmd-file --> What it actually says
Google Calendar MCP Server Copilot Instructions
This is a Model Context Protocol (MCP) server project for Google Calendar integration. Please follow these guidelines when working with this codebase:
Project Overview
- This is an MCP server that provides tools for Google Calendar API integration
- Built with TypeScript and uses the @modelcontextprotocol/sdk
- Handles OAuth authentication, event management, and calendar operations
- Follows the Model Context Protocol specification
MCP Resources
You can find more info and examples at https://modelcontextprotocol.io/llms-full.txt
Code Guidelines
- TypeScript Best Practices: Use strict typing, proper error handling, and follow the existing code patterns
- MCP Protocol: All tools must follow the MCP tool schema format with proper input validation using Zod
- Google Calendar API: Use the googleapis library and handle authentication properly
- Error Handling: Return structured error responses that follow the MCP format
- Security: Never expose sensitive credentials in logs or responses
Tool Development
When adding new tools:
- Define proper Zod schemas for input validation
- Create corresponding ToolSchema definitions
- Implement async handlers with proper error handling
- Return structured responses with success/error states
- Add comprehensive JSDoc comments
Authentication
- Uses Google Service Account authentication
- Environment variables are loaded from .env file
- Handle token refresh and error scenarios gracefully
Testing
- Test all tools manually using MCP-compatible clients
- Validate input schemas and error cases
- Ensure proper integration with Google Calendar API
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.
- 5d ago First seen · 40 lines · 373 tokens per session scan C 24da7de90d57
Google-Calendar-MCP-Server copilot-instructions.md is an instructions file published in the GitHub repository peadams21/Google-Calendar-MCP-Server (0 stars, last pushed 1y ago), licensed MIT. It adds 373 tokens to every session, about $0.0019 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other instructions, from other repositories
spellbook AGENTS.md
AGENTS.md instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
codemark GEMINI.md
Gemini CLI instructions for DanielCardonaRojas/codemark, covering development workflow and debugging with the tui logging system.
vrchat-mcp AGENTS.md
AGENTS.md instructions for BASIC-BIT/vrchat-mcp, covering agents, tool ergonomics goals (distilled), curated output philosophy, specific notes (current direction) and caching considerations (planned).
minimalist copilot-instructions.md
Instructions for DivyeshJayswal/minimalist, covering minimalist (coding tasks), persistence, fast path, bias and output.
totem AGENTS.md
AGENTS.md instructions for mmnto-ai/totem, covering totem: agent instructions, what totem is, session start protocol (mandatory), essentials and totem workflow.
front-mcp CLAUDE.md
Claude Code instructions for wearehoust/front-mcp, a project described as: Secure MCP server for Front.com: search conversations, manage contacts, send messages, automate inbox workflows — 26 tools, 172 actions.