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.
curl -O https://raw.githubusercontent.com/amikai/openings-mcp/main/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/amikai/openings-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/amikai/openings-mcp/release)<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.
<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>- NVIDIA SkillSpector warn
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.
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 | $0.00026 | $0.00616 |
| Sonnet 5 | $0.00010 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00123 |
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 9d 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 — 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:
providerOrderincmd/verify-companies/main.go): per provider, sample 3–5 companies frominternal/provider/<name>/companies.yaml;search_jobs_by_companymust return live listings for each, andget_job_detail_by_companymust succeed on at least one returned job_id. - Dedicated-tool providers (job boards and careers sites: the
Register*calls innewServer,cmd/openings-mcp/main.go): per provider, 3–5 varied<name>_search_jobsqueries exercising the filters it supports (keyword, location, ...) plus one<name>_get_job_detailon 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:
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.
- 9d ago First seen · 119 lines · 51 tokens per session scan A 84f9f63cda6a
release is a skill published in the GitHub repository amikai/openings-mcp (92 stars, last pushed 14d ago), licensed MIT. It adds 51 tokens to every session and 1,233 once invoked, about $0.0003 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
release
Cut a release of steam-games-mcp — draft CHANGELOG entries, check docs/metadata consistency, then bump/tag/push. Use when asked to release, cut a version, or publish a new version of this package.
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…
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-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…