Borrowing it
Nothing to install: this file belongs to cmer81/open-meteo-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/cmer81/open-meteo-mcp/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/cmer81/open-meteo-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/cmer81/open-meteo-mcp/release)<a href="https://agentmods.dev/skills/cmer81/open-meteo-mcp/release"><img src="https://agentmods.dev/badge/skills/cmer81/open-meteo-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/cmer81/open-meteo-mcp/release"><img src="https://agentmods.dev/badge/skills/cmer81/open-meteo-mcp/release.svg" alt="Reviewed on agentmods" width="80" 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.00554 |
| Opus 5.5 | $0.00022 | $0.00222 |
| Sonnet 5.5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00055 |
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 24d 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.
What it actually says
Releasing
Never run npm publish locally — publishing is automated and a version number is burned permanently once used. .github/workflows/release.yml triggers on any v* tag, fails if the tag does not match the package.json version, then runs npm ci → npm test → npm run build → npm audit → npm publish --provenance, creates the GitHub release, and only then builds and pushes the Docker image to GHCR.
1. Pre-release verification
npm test mocks the network, so it cannot tell whether the server still works. Both of these must be green before tagging:
npm run build && npm run smoke # every tool, once, against the live API
npm audit --audit-level high --omit=dev
npm run smoke (scripts/smoke-test.mjs) starts the built server over stdio with a real MCP client and calls all 17 tools. It is the only check that catches a tool publishing an empty input schema (see .claude/rules/tool-schemas.md).
2. Prepare main
- Land the changes on
main(the tag is cut from whatevermainpoints at). - Add the version's entry to
CHANGELOG.mdand commit it —npm versioncreates the release commit immediately after, so a changelog added later lands in the next release.
3. Tag
npm run release:patch # 2.0.2 -> 2.0.3
npm run release:minor # 2.0.2 -> 2.1.0
npm run release:major # 2.0.2 -> 3.0.0
Each runs npm version <level> && git push origin main --tags, which triggers the workflow. Confirm with the user before running it.
4. After publishing
npm takes a few minutes to serve the new version. npm view open-meteo-mcp-server version returning the previous number right after a publish is propagation lag, not a failed release — confirm with the workflow log, which ends with + open-meteo-mcp-server@<version>.
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.
- 24d ago First seen · 40 lines · 54 tokens per session scan A 7e396950b56d
release is a skill published in the GitHub repository cmer81/open-meteo-mcp (72 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 554 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-10-04.
Other skills, from other repositories
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
release-engineering
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags, versioning and artifact management (SemVer, conventional commits, changelogs, SBOM/provenance), readiness and quality gates…
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
verified-delivery
Implement and deliver an authorized change end to end — verify, open the PR, merge, and confirm post-merge state — using live-state gates, durable interruption handoffs, and live-state-first resumption. Use when a user grants end-to-end delivery authority for a specific change and the work may cross tool-call limits…
deployment-safety
Production deployment rules, rollback-first recovery, dependency batching, CI cost awareness, framework upgrade verification, fallback observability, and GitHub repo settings standardization.
publish-npm-package
Configure or troubleshoot npm package publication with GitHub Actions and npm Trusted Publishing. Use this skill for JavaScript or TypeScript packages. Also use it for the npm package in a mixed-language repository. Do not use it for applications or repositories without an npm package. Do not use it for generic CI…