Borrowing it
Nothing to install: this file belongs to shwetank-dev/mcp-server-calendly. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shwetank-dev/mcp-server-calendly/main/CLAUDE.mdgit clone --depth 1 https://github.com/shwetank-dev/mcp-server-calendlyWrote 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/shwetank-dev/mcp-server-calendly/claude-md)<a href="https://agentmods.dev/instructions/shwetank-dev/mcp-server-calendly/claude-md"><img src="https://agentmods.dev/badge/instructions/shwetank-dev/mcp-server-calendly/claude-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.00442 | $0.00442 |
| Opus 5 | $0.00221 | $0.00221 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
mcp-server-calendly CLAUDE.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.
What it actually says
Calendly MCP Server
MCP server providing Calendly scheduling functionality via Calendly's REST API v2.
Architecture
src/
├── index.ts # MCP server + stdio entrypoint
├── client.ts # HTTP client for Calendly API
└── types.ts # TypeScript types for API responses
Critical
- Package name:
@nimblebraininc/calendly(npm-style, matches GitHub org) - Manifest uses Node.js:
node dist/index.js - Server uses
@modelcontextprotocol/sdkwith stdio transport
user_config
API key configured via manifest user_config, not hardcoded:
{
"user_config": {
"api_key": {
"type": "string",
"sensitive": true,
"required": true
}
},
"server": {
"mcp_config": {
"env": { "CALENDLY_API_KEY": "${user_config.api_key}" }
}
}
}
Available Tools
| Category | Tools |
|---|---|
| User | get_current_user |
| Event Types | list_event_types |
| Events | list_scheduled_events, get_event, cancel_event |
| Invitees | list_invitees |
| Availability | check_availability |
Calendly API Reference
- Base URL:
https://api.calendly.com - Auth: Bearer token
- Docs: https://developer.calendly.com/api-docs
Commands
npm run build # Compile TypeScript
npm run dev # Run with tsx (dev)
npm run test # Test
npm run lint # Lint
npm run format # Format
npm run typecheck # Type check
make check # All checks
Local Testing with mpak
mpak config set @nimblebraininc/calendly api_key=your_key_here
mpak run @nimblebraininc/calendly
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 · 74 lines · 442 tokens per session scan A 86f25bd8aa02
mcp-server-calendly CLAUDE.md is an instructions file published in the GitHub repository shwetank-dev/mcp-server-calendly (0 stars, last pushed 6mo ago), licensed MIT. It adds 442 tokens to every session, about $0.0022 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-31.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.