A release workflow for the openings-mcp project, covering version checks, provider tests, tagging, and release-note updates.

Use it to release a new version, test providers before release, and rewrite automatically generated release notes.

It removes the need to remember and manually coordinate the many checks involved in publishing a new version.

How amikai/openings-mcp configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to amikai/openings-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.

Copy the file

curl -O https://raw.githubusercontent.com/amikai/openings-mcp/main/.agents/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/amikai/openings-mcp

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/amikai/openings-mcp/release/github.svg)](https://agentmods.dev/skills/amikai/openings-mcp/release)

Your own site

<a href="https://agentmods.dev/skills/amikai/openings-mcp/release"><img src="https://agentmods.dev/badge/skills/amikai/openings-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/amikai/openings-mcp/release"><img src="https://agentmods.dev/badge/skills/amikai/openings-mcp/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,233 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Excessive Agency · line 73
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00051	$0.01233
Opus 5.5	$0.00020	$0.00493
Sonnet 5.5	$0.00010	$0.00247
Haiku 4.5	$0.00005	$0.00123

Measured 2mo ago against content hash 84f9f63cda6a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.agents/skills/release/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release

Overview

Cut a release end to end: validate the version, live-smoke-test every provider at HEAD, push the tag, wait for the Release workflow (goreleaser publishes the GitHub release with a raw commit-list body), then rewrite the notes in the house style and report back.

Input

Exactly one version matching ^v\d+\.\d+\.\d+$ (all numeric, e.g. v0.8.0). Reject anything else — 0.8.0, v0.8, v0.8.0-rc1 — and ask for a corrected version instead of guessing. It must not already exist and must sort above the latest tag (git tag --sort=-v:refname | head -1 — that latest tag is also the "previous version" used in steps 2, 4, and 5). Require a clean tree on main, in sync with origin/main.

1. Smoke-test every provider (before tagging)

Test HEAD through the real MCP path, never an installed binary or the session's connected openings-mcp server — those run the previous release. Build once (go build -o <scratchpad>/openings-mcp ./cmd/openings-mcp) and drive it over stdio; the request script is in the integrate-new-provider skill's MCP-surface step.

ATS adapters (the unified-search set: providerOrder in cmd/verify-companies/main.go): per provider, sample 3–5 companies from internal/provider/<name>/companies.yaml; search_jobs_by_company must return live listings for each, and get_job_detail_by_company must succeed on at least one returned job_id.
Dedicated-tool providers (job boards and careers sites: the Register* calls in newServer, cmd/openings-mcp/main.go): per provider, 3–5 varied <name>_search_jobs queries exercising the filters it supports (keyword, location, ...) plus one <name>_get_job_detail on a returned identifier.

A failure stops the release: retry once to rule out upstream flakiness, then report to the user instead of tagging. Also run go test ./... — cheaper to catch breakage here than across six CI matrix legs after the tag is public.

2. Tag

Annotated, message in the same shape as the release title:

Read the full file on GitHub · 119 lines

Changes

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.

2mo ago First seen · 119 lines · 51 tokens per session scan A 84f9f63cda6a

Subscribe to this mod's changes

release is a skill published in the GitHub repository amikai/openings-mcp (108 stars, last pushed 11d ago), licensed MIT. It adds 51 tokens to every session and 1,233 once invoked, about $0.0002 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.

Git and workflow Go Releases job-board job-search llm-tools mcp mcp-server

release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releaseamikai/openings-mcp	Skill	108	11d ago	MIT	A	51	Claude Code, Codex
changelog-styleGrinv/steam-games-mcp	Skill	5	yesterday	MIT	A	50	Claude Code, Codex
releaseGrinv/steam-games-mcp	Skill	5	yesterday	MIT	A	47	Claude Code, Codex
git-wrapupcyanheads/pubchem-mcp-server	Skill	12	9d ago	Apache-2.0	A	109	Claude Code
release-and-publishcyanheads/pubchem-mcp-server	Skill	12	9d ago	Apache-2.0	A	155	Claude Code
release-pr-reviewcyanheads/pubchem-mcp-server	Skill	12	9d ago	Apache-2.0	A	136	Claude Code
release-and-publishcyanheads/calculator-mcp-server	Skill	3	9d ago	Apache-2.0	A	155	Claude Code

openings-mcp: Skill for Claude Code