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/codester1000/raindrop-mcp/claude-mdgit clone --depth 1 https://github.com/codester1000/raindrop-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/codester1000/raindrop-mcp/claude-md)<a href="https://agentmods.dev/instructions/codester1000/raindrop-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/codester1000/raindrop-mcp/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 | $0.03037 | $0.03037 |
| Opus 5 | $0.01519 | $0.01519 |
| Sonnet 5 | $0.00607 | $0.00607 |
| Haiku 4.5 | $0.00304 | $0.00304 |
Grade A, and why
raindrop-mcp 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 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Raindrop MCP Project Guidelines
Project Overview
Raindrop MCP is a Model Context Protocol (MCP) server that provides AI assistants with access to Raindrop.io bookmark management functionality. It implements dynamic resource handling, real-time API integration, and comprehensive tool support.
Version Information
- Current version: 2.0.11
- Node.js: >=18.0.0 required
- Bun: >=1.0.0 required
- MCP SDK: ^1.17.1
Key Features
- ✅ Full MCP Protocol Compliance: Implements MCP SDK v1.17.1 with proper tool/resource registration
- ✅ Dynamic Resource System: Access any collection or bookmark by ID without pre-registration
- ✅ Real-time API Data: Resources fetch live data from Raindrop.io APIs on-demand
- ✅ Comprehensive Testing: 11 test cases with real API validation
- ✅ Type Safety: Full TypeScript implementation with Zod validation schemas
External References
Core Documentation
- Raindrop.io API Documentation
- MCP Documentation
- Model Context Protocol with LLMs
- MCP Typescript SDK v1.17.1
Development Resources
- Example MCP servers repository
- MCP Boilerplate
- MCP Inspector Tool
- This project on GitHub
- systemprompt-mcp-server
Installation and Usage
NPM Package
npx @adeze/raindrop-mcp@latest
Development Commands
- Development:
bun run dev(watch STDIO mode) orbun run dev:http(watch HTTP mode) - Production:
bun run start:prod(from build) orbun run run(CLI executable) - HTTP Server:
bun run start:http(starts HTTP transport on port 3002) - Type checking:
bun run type-check - Testing:
bun run testorbun run test:coverage - Building:
bun run build(creates build/ directory with index.js and server.js) - Debugging:
- MCP Inspector STDIO:
bun run inspector - MCP Inspector HTTP:
bun run inspector:http-server
- MCP Inspector STDIO:
- Maintenance:
bun run clean(removes build/),bun run dxt:pack(creates DXT package) - Versioning:
bun run bump:patch|minor|major
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 · 308 lines · 3,037 tokens per session scan A 3af292bdfc47
raindrop-mcp CLAUDE.md is an instructions file published in the GitHub repository codester1000/raindrop-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 3,037 tokens to every session, about $0.0152 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.