Borrowing it
Nothing to install: this file belongs to adeze/raindrop-mcp. 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/adeze/raindrop-mcp/master/.github/skills/publishing/SKILL.mdgit 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/publishing)<a href="https://agentmods.dev/skills/adeze/raindrop-mcp/publishing"><img src="https://agentmods.dev/badge/skills/adeze/raindrop-mcp/publishing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/adeze/raindrop-mcp/publishing"><img src="https://agentmods.dev/badge/skills/adeze/raindrop-mcp/publishing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.00357 |
| Opus 5.5 | $0.00006 | $0.00143 |
| Sonnet 5.5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
publishing 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 1mo 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.
What it actually says
Publishing Skill for @adeze/raindrop-mcp
Use this workflow for all standard releases in this repository.
Source of Truth
- Release command:
bun run release - Release config:
.releaserc.json - CI trigger:
.github/workflows/ci.ymlon push tomaster
Standard Release Flow
- Merge Conventional Commit-based changes to
master. - CI runs lint, type-check, tests, and build.
- CI release job runs
semantic-release. semantic-releasecomputes version, updatesCHANGELOG.md, tags release, publishes npm, and creates a GitHub Release.- Release prepare step syncs
manifest.jsonand buildsraindrop-mcp.mcpbso the bundle is attached to the GitHub Release.
Required Secrets
GITHUB_TOKEN: provided by GitHub Actions.
Publishing Authentication
- npm publish uses GitHub Actions OIDC trusted publishing.
- No long-lived npm token is required for the standard CI release path.
Local Verification Before Merge
bun run lint
bun run type-check
bun run test
bun run build
Conventional Commit Examples
fix: handle missing collection id in bulk editfeat: add includeArchived filter to bookmark_searchfeat!: remove deprecated query parameter
Rules
- Do not manually bump package versions for standard releases.
- Do not manually create release tags for standard releases.
- Do not run manual npm publish commands for standard releases.
- Keep release behavior in
.releaserc.jsonand CI workflow aligned.
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.
- 1mo ago First seen · 54 lines · 14 tokens per session scan A 16565f78927e
publishing is a skill published in the GitHub repository adeze/raindrop-mcp (189 stars, last pushed 10d ago), licensed MIT. It adds 14 tokens to every session and 357 once invoked, about $0.0001 per session on Opus 5.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
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.
github-ops
GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.