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/copilot-instructionsgit clone --depth 1 https://github.com/codester1000/raindrop-mcpWhat 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.00700 | $0.00700 |
| Opus 5 | $0.00350 | $0.00350 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
raindrop-mcp copilot-instructions.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 2d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot & AI Assistant Instructions
General Coding Principles
- Write modular, well-documented, and maintainable code.
- Use modern, type-safe, idiomatic TypeScript. Prefer interfaces for object types and camelCase/PascalCase naming conventions.
- Use zod for schema validation where appropriate.
- Use async/await for all asynchronous code.
- Group imports by type (external, then internal).
- Use try/catch for error handling with descriptive messages.
- Prefer explicitness and reference documentation or example repos if ambiguous.
Raindrop.io & MCP API Coverage
- Ensure complete coverage for Raindrop.io and MCP endpoints.
- Reference Raindrop.io API docs for endpoints, authentication, and data models.
- Reference
raindropio/appfor implementation details and usage patterns. - LLM friendly documentation is
https://context7.com/context7/developer_raindrop_io/llms.txt - Reference Model Context Protocol docs and LLMs integration guide for MCP compliance.
- Reference MCP TypeScript SDK for usage patterns.
Project Structure
- Source:
src/ - Build:
build/ - Tests:
tests/(all test files must be here)
Development Best Practices
- Structure tools with clear schemas, validation, and consistent JSON responses.
- Include documentation and setup instructions.
- Use design patterns for maintainability and scalability.
- Use helper functions to reduce duplication.
- Prefer declarative programming styles and common libraries/utilities.
- Use
bunfor package management/scripts (not npm).
Testing
- Use Vitest for all tests.
- Validate tool calls return properly structured responses.
- Verify manifest loads and host integration works.
Tooling & References
- For debugging MCP servers, see MCP Debugging Instructions.
- Use Inspector tool and repo for protocol inspection.
- Use
#concept7for documentation access and reference for SDKs, APIs, and protocol details. - MCP Protocol spec: specification
- MCP server examples:
modelcontextprotocol/serverstypescript-sdk/src/examples/README.md - LLM-friendly docs: context7.com/context7/developer_raindrop_io/llms.txt
- MCP boilerplate:
cyanheads/mcp-ts-template
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.
- 2d ago First seen · 63 lines · 700 tokens per session scan A d549c6dfa1ad
raindrop-mcp copilot-instructions.md is an instructions file published in the GitHub repository codester1000/raindrop-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 700 tokens to every session, about $0.0035 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.