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/84emllc/calendly-mcp-server/agents-mdgit clone --depth 1 https://github.com/84emllc/calendly-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/84emllc/calendly-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/84emllc/calendly-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/84emllc/calendly-mcp-server/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.01448 | $0.01448 |
| Opus 5 | $0.00724 | $0.00724 |
| Sonnet 5 | $0.00290 | $0.00290 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
calendly-mcp-server 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 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.
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.
This is a copy
100% identical to calendly-mcp-server CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calendly MCP Server
Common Commands
npm run build: Build TypeScript to JavaScriptnpm run dev: Run in development mode with tsxnpm start: Run the built servernpm install: Install dependencies
Testing the Server
- Use MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.js - Test with Claude Desktop: Add to config file
- Direct testing:
node dist/index.js(requires MCP client)
Project Structure
src/
├── index.ts # Main MCP server entry point
├── types.ts # TypeScript interfaces and types
├── calendly-client.ts # Calendly API client class
└── tools/
├── oauth-tools.ts # OAuth authentication tools
├── api-tools.ts # Calendly API tools
├── scheduling-tools.ts # Scheduling API tools
└── tool-definitions.ts # MCP tool schema definitions
Code Style
- Use ES modules (import/export), not CommonJS
- Use TypeScript with strict type checking
- Use
as constfor literal types in MCP responses - Destructure imports when possible
- Keep tool classes focused on single responsibility
Environment Variables
Calendly API (Required)
CALENDLY_API_KEY: Personal Access Token (for simple auth)CALENDLY_CLIENT_ID+CALENDLY_CLIENT_SECRET: OAuth credentialsCALENDLY_ACCESS_TOKEN+CALENDLY_REFRESH_TOKEN: OAuth tokens
Calendly Optional (Recommended)
CALENDLY_USER_URI: User URI for automatic defaults (e.g.,https://api.calendly.com/users/your_user_id)CALENDLY_ORGANIZATION_URI: Organization URI for automatic defaults
Development Workflow
- Make changes to TypeScript files in
src/ - Run
npm run buildto compile - Test with MCP Inspector or Claude Desktop
- IMPORTANT: Always test authentication before committing
- Run
npm run buildagain if there are TypeScript errors - Use conventional commit messages (see Git Guidelines below)
Git Guidelines (Conventional Commits)
Use this format: <type>[optional scope]: <description>
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 · 150 lines · 1,448 tokens per session scan A 363bc16da8c4
calendly-mcp-server AGENTS.md is an instructions file published in the GitHub repository 84emllc/calendly-mcp-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,448 tokens to every session, about $0.0072 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to calendly-mcp-server CLAUDE.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
postfast-mcp CLAUDE.md
Instructions for peturgeorgievv-factory/postfast-mcp, covering claude.md, rules and release (tag-triggered — ci holds no credentials).
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
seekstone CLAUDE.md
Claude Code instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
Plonk AGENTS.md
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
cyxj-groksearch CLAUDE.md
Claude Code instructions for chenyuxiaojin/cyxj-groksearch, covering claude.md, 常用命令 and 结构与坑.