Borrowing it
Nothing to install: this file belongs to The-OpenROAD-Project/OpenROAD-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/The-OpenROAD-Project/OpenROAD-MCP/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/The-OpenROAD-Project/OpenROAD-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/the-openroad-project/openroad-mcp/release)<a href="https://agentmods.dev/skills/the-openroad-project/openroad-mcp/release"><img src="https://agentmods.dev/badge/skills/the-openroad-project/openroad-mcp/release/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/the-openroad-project/openroad-mcp/release"><img src="https://agentmods.dev/badge/skills/the-openroad-project/openroad-mcp/release.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.00163 | $0.01673 |
| Opus 5.5 | $0.00065 | $0.00669 |
| Sonnet 5.5 | $0.00033 | $0.00335 |
| Haiku 4.5 | $0.00016 | $0.00167 |
Grade A, and why
release 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Preparation
This skill automates the full release preparation workflow for the openroad-mcp project. It ensures every file that references the version gets updated consistently.
Project context
- Build system: npm / Node.js 22
- Version source:
typescript/package.json.versionfield - Changelog format: Keep a Changelog
- GitHub repo:
The-OpenROAD-Project/openroad-mcp - Release gatekeeper: @vvbandeira (org member) — must approve and merge all releases
Workflow
Step 1: Determine versions
Read the current version from typescript/package.json:
jq -r '.version' typescript/package.json
Then ask the user what the new version should be. Suggest the next logical semver bump based on the commits since the last release:
- Patch (0.3.0 → 0.3.1): only fixes and minor changes
- Minor (0.3.0 → 0.4.0): new features added, backwards compatible
- Major (0.3.0 → 1.0.0): breaking changes
Show the suggestion but let the user decide.
Step 2: Collect commits since last release
Get the last release tag:
git tag --sort=-v:refname | head -5
Then list all commits since that tag:
git log <last-tag>..HEAD --oneline
If no tag exists, use the first commit or the last "chore: release" commit:
git log --oneline --grep="chore: release" | head -1
Step 3: Categorize commits into changelog sections
Read each commit message and sort into Keep a Changelog categories. Commits may use conventional prefixes or plain one-liner sentences — both are accepted:
| Category | Prefixed form | Plain form (keyword) |
|---|---|---|
| Added | feat: |
sentence mentions "add", "new", "ship" |
| Changed | chore:, ci:, build:, refactor:, docs: |
anything else |
| Fixed | fix: |
sentence mentions "fix", "correct", "repair" |
For each commit, format the changelog entry as:
- Description ([#PR](https://github.com/The-OpenROAD-Project/openroad-mcp/pull/PR))
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +2 lines 126f69f8b5db
- 1mo ago First seen · 188 lines · 163 tokens per session scan A cdb7cdf0a02f
release is a skill published in the GitHub repository The-OpenROAD-Project/OpenROAD-MCP (30 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 163 tokens to every session and 1,673 once invoked, about $0.0007 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
omh-deploy-and-monitor
This is an OMH deploy-and-monitor workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-release-cut
This is an OMH release-cut workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
release-rollback
Plan and execute authorized release promotion or rollback with exact artifact and data compatibility. Use when deploying versions, changing traffic or recovering a bad release; do not equate reversing code with restoring data.