Borrowing it
Nothing to install: this file belongs to 84emllc/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.
curl -O https://raw.githubusercontent.com/84emllc/google-calendar-mcp/main/.claude/skills/mcp-research/SKILL.mdgit clone --depth 1 https://github.com/84emllc/google-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/skills/84emllc/google-calendar-mcp/mcp-research)<a href="https://agentmods.dev/skills/84emllc/google-calendar-mcp/mcp-research"><img src="https://agentmods.dev/badge/skills/84emllc/google-calendar-mcp/mcp-research/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/84emllc/google-calendar-mcp/mcp-research"><img src="https://agentmods.dev/badge/skills/84emllc/google-calendar-mcp/mcp-research.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00923 |
| Opus 5 | $0.00000 | $0.00462 |
| Sonnet 5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
mcp-research 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 10d 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 mcp-research — 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Implementation Research
Quick Start
What are you doing?
- 📝 Reviewing MCP server →
references/implementation-checklist.md - 🚀 Planning MCP feature →
references/protocol-patterns.md - 🐛 Protocol issue →
references/common-pitfalls.md - ✅ Architecture validation → All references + latest spec
Research Workflow
- Understand implementation - What MCP capabilities? Which transport? What security requirements?
- Consult references - Load relevant reference files progressively
- Check latest spec - WebFetch
https://modelcontextprotocol.io/specification/2025-06-18 - Search community - WebSearch for "MCP [specific-issue] 2025"
- Validate compliance - Protocol compliance, security, best practices
- Report findings - Structured format (see examples/)
Critical MCP Requirements
Protocol Compliance (JSON-RPC 2.0)
- All messages MUST include
jsonrpc: "2.0" - Responses include
resultORerror, never both - Initialization:
initialize→ response →initializednotification - Use standard error codes (-32xxx)
Security & Consent
- User consent MUST be obtained before data access
- Tool execution requires explicit approval
- No hardcoded credentials
- Input/output sanitization required
Capability Advertisement
- Declare all capabilities in
initializeresponse - Types:
tools,resources,prompts,logging,experimental - Protocol version:
"2025-06-18"(latest)
Transport Layers
stdio:
- Newline-delimited JSON-RPC messages
- Use stderr for logging (not stdout)
- Flush after each message
HTTP/SSE:
- POST
/mcpfor JSON-RPC requests - GET
/mcp/ssefor server-sent events - CORS configured for browser clients
Key Reference Files
implementation-checklist.md - Protocol compliance, capabilities, security, production readiness
protocol-patterns.md - Tool/resource/prompt patterns, best practices, code examples
common-pitfalls.md - Known issues, edge cases, gotchas
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 117 lines · 0 tokens per session scan A d96ff92ef735
mcp-research is a skill published in the GitHub repository 84emllc/google-calendar-mcp (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 923 tokens. A static security scan graded it A with 0 findings. It is 100% identical to mcp-research, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
split-to-prs
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
agreement-setup
Set up a bKash tokenized agreement for repeat charges and check its status.
planfix-api
A Planfix CRM integration for managing tasks and contacts. A CRM is a system for organizing customer and business relationships.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).