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 skills/adeze/raindrop-mcp/dxt-packagingnpx skills add adeze/raindrop-mcp --skill dxt-packaginggit clone --depth 1 https://github.com/adeze/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/skills/adeze/raindrop-mcp/dxt-packaging)<a href="https://agentmods.dev/skills/adeze/raindrop-mcp/dxt-packaging"><img src="https://agentmods.dev/badge/skills/adeze/raindrop-mcp/dxt-packaging.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.00017 | $0.00481 |
| Opus 5 | $0.00009 | $0.00241 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
dxt-packaging 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCPB Packaging Skill (DXT legacy)
Guidelines for building and packaging MCP servers as MCP Bundles (MCPB). DXT references are legacy.
Overview
MCP Bundles (MCPB) allow AI assistants to discover and use MCP servers from a package archive. This skill covers the complete MCPB development workflow.
Getting Started
Read the Specifications
- Architecture & Overview: https://github.com/anthropics/mcpb
- MCPB Repository: https://github.com/anthropics/mcpb
README.md- Architecture overview, capabilities, and integration patternsMANIFEST.md- Complete bundle manifest structure and field definitionsexamples/- Reference implementations including a "Hello World" example
Create Proper Bundle Structure
- Generate a valid
manifest.jsonfollowing the MANIFEST.md spec - Implement an MCP server using
@modelcontextprotocol/sdkwith proper tool definitions - Include proper error handling and timeout management
Development Best Practices
MCP Protocol Communication
- Implement proper MCP protocol communication via stdio transport
- Structure tools with clear schemas, validation, and consistent JSON responses
- Make use of the fact that this bundle will be running locally
Logging & Debugging
- Add appropriate logging and debugging capabilities
- Use structured logging for error tracking
- Include proper documentation and setup instructions
Testing Considerations
- Validate that all tool calls return properly structured responses
- Verify manifest loads correctly and host integration works
- Generate complete, production-ready code that can be immediately tested
- Focus on defensive programming and clear error messages
- Follow the exact MCPB specifications to ensure ecosystem compatibility
Key Files
- manifest.json - Bundle metadata and configuration
- src/index.ts - Main entry point for the MCP server
- build/ - Compiled output for distribution
References
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 · 64 lines · 17 tokens per session scan A 2f92270331b8
dxt-packaging is a skill published in the GitHub repository adeze/raindrop-mcp (183 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 481 once invoked, about $0.0001 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-30.
Other skills, from other repositories
discovery-distribution
Run the discovery → synthesis → build → verify → elite-package → distribute loop to turn domain insight into a multi-surface, verified GitHub product. Use when productizing an idea, packaging agentic systems, or raising a repo to elite open-source standards before launch.
vinkius-deploy
How to deploy MCP servers to Vinkius Edge using mcpfusion deploy. Use this skill whenever deploying, configuring remote settings, preparing an entrypoint for edge deployment, or troubleshooting deploy-related errors. Activate when the user says "deploy", "publish to edge", "mcpfusion deploy", "push to Vinkius"…
verifying-compose-ui
Verifying Compose UI by rendering components or previews and inspecting the resulting images and state transitions. Activate for visual behavior that requires runtime rendering; use ordinary tests for nonvisual logic.
ingest-gradle-upgrade
Ingests a Gradle wrapper upgrade for this repository: reads the release notes, upgrade guides, and linked documentation for the version upgraded to, then updates this repo's own code/tooling and the shipped Gradle MCP skills (src/main/skills/) so everything stays accurate for that version. Positive Triggers (when to…
authoring-gradle-builds
Authoring and modifying Gradle build logic, including settings, plugins, dependencies, tasks, conventions, and upgrades. Activate when build files or plugins must change; use using-gradle for inspection or execution without build-definition edits.
advanced-gradle-dependencies
Analyzing advanced Gradle dependency behavior, including resolution, variants, capabilities, conflicts, constraints, and publication metadata. Activate for dependency-resolution design or diagnosis; use authoring-gradle-builds for routine dependency declarations.