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/mcp-inspectorgit 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/mcp-inspector)<a href="https://agentmods.dev/instructions/codester1000/raindrop-mcp/mcp-inspector"><img src="https://agentmods.dev/badge/instructions/codester1000/raindrop-mcp/mcp-inspector.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.00371 | $0.00371 |
| Opus 5 | $0.00186 | $0.00186 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
raindrop-mcp mcp-inspector.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 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.
This is a copy
100% identical to raindrop-mcp mcp-inspector.instructions.md — 1 line 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.
What it actually says
MCP Inspector CLI Prompt
This prompt guides you to use the MCP Inspector tool in CLI mode for protocol inspection, debugging, and tool listing in a VS Code environment.
Prerequisites
- Ensure you have Node.js and npx installed.
- Install MCP Inspector:
npx -y @modelcontextprotocol/inspector --help - Build your MCP server (e.g.,
bun run buildor equivalent).
Usage Examples
List Available Tools
Run the following command in your VS Code terminal:
npx -y @modelcontextprotocol/inspector --cli node build/index.js --method tools/list
Send a Protocol Request (e.g., ping)
npx -y @modelcontextprotocol/inspector --cli node build/index.js --method ping
Debugging and Inspection
- Use Inspector CLI to wrap your MCP server and inspect protocol traffic.
- Example for STDIO server:
npx -y @modelcontextprotocol/inspector node build/index.js
- For HTTP server:
npx -y @modelcontextprotocol/inspector node build/server.js
Tips
- Use Inspector CLI flags for advanced filtering, logging, and output formatting. See Inspector documentation for details.
- Integrate Inspector CLI commands into your VS Code tasks or launch configurations for automated inspection and debugging.
- Use Vitest or your preferred test runner to automate CLI checks (see
tests/inspector.test.tsfor examples).
References
This prompt is designed for VS Code users working with MCP protocol servers and the Inspector tool in CLI mode.
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 · 60 lines · 371 tokens per session scan A 2494b77a1cd7
raindrop-mcp mcp-inspector.instructions.md is an instructions file published in the GitHub repository codester1000/raindrop-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 371 tokens to every session, about $0.0019 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to raindrop-mcp mcp-inspector.instructions.md, differing in 1 line, and is treated as a copy.
Other instructions, from other repositories
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).
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.
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.
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).