Borrowing it
Nothing to install: this file belongs to rhinocap/raven-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/rhinocap/raven-mcp/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/rhinocap/raven-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/rhinocap/raven-mcp/release)<a href="https://agentmods.dev/skills/rhinocap/raven-mcp/release"><img src="https://agentmods.dev/badge/skills/rhinocap/raven-mcp/release.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.00054 | $0.04660 |
| Opus 5 | $0.00027 | $0.02330 |
| Sonnet 5 | $0.00011 | $0.00932 |
| Haiku 4.5 | $0.00005 | $0.00466 |
Grade A, and why
release scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL "https://ravenmcp.ai/changelog?cb=$RANDOM" | grep -o 'cl-version">v[0-9.]*' | head -1 # must show vX.Y.Z How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release raven-mcp
The end-to-end release runbook for raven-mcp. scripts/release.sh does the mechanical work (version bump, manifest/server sync, .mcpb rebuild, npm publish, mcp-publisher publish, commit, tag, push) — but it has two gaps and one propagation step it does not handle, which is why releasing felt hard. This skill wraps it so a release is one predictable pass.
When to use
Any time merged work on main needs to reach Raven consumers — npm (raven-mcp), the public .mcpb at ravenmcp.ai, and your own machine's instances. Run AFTER the feature PR is merged to main, not before.
How Raven is actually consumed (why "merge to main" is not enough)
- Your Claude Code (CLI) instances load Raven from a local path, not npm:
~/.claude.jsonregistersravenasnode /Users/accunliffe/projects/raven-mcp/dist/index.js(both a globalmcpServers.ravenentry and a project-scoped one). They read the builtdist/, which is gitignored — so a new tool only reaches them afternpm run buildin this working copy AND the instance reconnects its MCP server (a stdio server is spawned once at session start). New sessions auto-pick-up the rebuilt dist; already-running sessions need/mcp→ reconnectraven(or a session restart). - npm package
raven-mcp(bin: raven-mcp → dist/index.js) — for any consumer wired vianpx raven-mcp/ a dependency. Only updates onnpm publish. - MCP Registry record
ai.ravenmcp/raven-mcp— the discovery metadata for the npm package and hosted remote. Only updates onmcp-publisher publish. - Claude Desktop extension
local.mcpb.andrew-cunliffe.raven-mcp— a separate packaged copy under~/Library/Application Support/Claude/Claude Extensions/. It does NOT read this working copy. It updates only when you rebuild the.mcpband reinstall the extension in Claude Desktop.
So a full release = publish npm + publish the MCP Registry record + rebuild/redeploy .mcpb + rebuild local dist + reconnect/reinstall.
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.
- 8d ago First seen · 191 lines · 54 tokens per session scan A cb33b62c6119
release is a skill published in the GitHub repository rhinocap/raven-mcp (6 stars, last pushed 15d ago), licensed Apache-2.0. It adds 54 tokens to every session and 4,660 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.