Borrowing it
Nothing to install: this file belongs to kazuph/mcp-raindrop. 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/kazuph/mcp-raindrop/master/CLAUDE.mdgit clone --depth 1 https://github.com/kazuph/mcp-raindropWrote 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/kazuph/mcp-raindrop/claude-md)<a href="https://agentmods.dev/instructions/kazuph/mcp-raindrop/claude-md"><img src="https://agentmods.dev/badge/instructions/kazuph/mcp-raindrop/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.04055 | $0.04055 |
| Opus 5 | $0.02027 | $0.02027 |
| Sonnet 5 | $0.00811 | $0.00811 |
| Haiku 4.5 | $0.00405 | $0.00405 |
Grade A, and why
mcp-raindrop 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 6d 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Raindrop MCP Project Guidelines
External References
- Raindrop.io API Documentation: https://developer.raindrop.io
- MCP Documentation: https://modelcontextprotocol.io/
- Model Context Protocol with LLMs
- MCP Typescript SDK v1.9.0
- Example MCP servers repository
- This project on GitHub
Installation and Usage
NPM Package
You can use this package directly from npm:
npx @kazuph/mcp-raindrop
Development Commands
- Build/Run:
bun run start(orbun run src/index.ts) - Development:
bun run dev(watch mode) - Type checking:
bun run type-check - Tests:
bun run test - Run single test:
bun test src/tests/mcp.service.test.ts - Test with coverage:
bun run test:coverage - Debug:
bun run debugorbun run inspector(runs with MCP inspector) - Build:
bun run build(builds to build directory) - Clean:
bun run clean(removes build directory) - HTTP server:
bun run start:http(starts with HTTP transport)
Code Style
- TypeScript with strict type checking
- ESM modules (
import/export) with.jsextension in imports - Use Zod for validation and schema definitions
- Use Axios for API requests
- Class-based services with dependency injection
- Functional controllers with try/catch error handling
- Use error objects with status codes and messages
- Resource-based MCP design using ResourceTemplate where appropriate
Conventions
- Imports: Group imports by type (external, internal)
- Naming: camelCase for variables/functions, PascalCase for classes/types
- Error handling: Use try/catch blocks with descriptive error messages
- Type definitions: Prefer interfaces for object types
- Async: Use async/await pattern consistently
- Testing: Use Vitest with mocks for dependencies
- Tests should be co-located with source files in
src/testsdirectory
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.
- 6d ago First seen · 351 lines · 4,055 tokens per session scan A ff351f8ffb59
mcp-raindrop CLAUDE.md is an instructions file published in the GitHub repository kazuph/mcp-raindrop (0 stars, last pushed 7mo ago), licensed MIT. It adds 4,055 tokens to every session, about $0.0203 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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.