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.svg" alt="Measured on agentmods" 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 | $0.00081 | $0.00837 |
| Sonnet 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 3d 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.
- 3d ago Changed · +2 lines 126f69f8b5db
- 8d 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 (17 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 163 tokens to every session and 1,673 once invoked, about $0.0008 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
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
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, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
release-notes
Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.
github
Use when automating GitHub issues, pull requests, reviews, CI checks, labels, releases, or engineering collaboration loops through the GitHub CLI.
finalize
Finalize orphaned recordings - stop processes, compress, push to orphan branch. TRIGGERS - finalize recording, stop asciinema, orphaned recording.