Borrowing it
Nothing to install: this file belongs to AI-Riksarkivet/ra-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/AI-Riksarkivet/ra-mcp/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/AI-Riksarkivet/ra-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/ai-riksarkivet/ra-mcp/release)<a href="https://agentmods.dev/skills/ai-riksarkivet/ra-mcp/release"><img src="https://agentmods.dev/badge/skills/ai-riksarkivet/ra-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/ai-riksarkivet/ra-mcp/release"><img src="https://agentmods.dev/badge/skills/ai-riksarkivet/ra-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.00070 | $0.00684 |
| Opus 5 | $0.00035 | $0.00342 |
| Sonnet 5 | $0.00014 | $0.00137 |
| Haiku 4.5 | $0.00007 | $0.00068 |
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
Cut a new release for the ra-mcp project.
Workflow
-
Determine current state — run these in parallel:
git tag --sort=-v:refname | head -5to find the latest taggrep '^version' pyproject.toml | head -1to find the current versiongit log --oneline $(git describe --tags --abbrev=0)..HEADto list commits since the last tag
-
Decide the version bump — follow semver based on conventional commits:
- patch (0.x.Y): only
fix,refactor,perf,docs,style,test,build,ci,chore - minor (0.X.0): any
featcommit - major (X.0.0): any commit with
!orBREAKING CHANGEfooter - If the user specified a version, use that instead
- patch (0.x.Y): only
-
Confirm with the user — show:
- Current version and proposed next version
- Summary of commits going into the release
- Ask for approval before proceeding
-
Cut the release — run:
make release VERSION=<version>This bumps
pyproject.toml, commits, tags, and pushes. The tag push triggers two CI workflows in parallel:release.yml(changelog + GitHub Release) andpublish.yml(Docker build, push, sign, and attestations). -
Monitor CI workflows — after the tag push, watch both workflows:
- Run
gh run list --limit 5to find the triggered runs - Poll with
gh run view <run-id>until both "Release" and "Publish" workflows complete (check every ~30 seconds) - If either workflow fails, run
gh run view <run-id> --log-failedto get the error details and report them to the user - Only proceed to the report step once both workflows succeed
- Run
-
Report — confirm the tag was pushed and link to the GitHub releases page:
https://github.com/AI-Riksarkivet/ra-mcp/releases
Rules
- ALWAYS confirm the version with the user before running
make release - NEVER skip the confirmation step
- If there are uncommitted changes, warn the user and stop
- If there are no new commits since the last tag, tell the user and stop
- When making any git commits (e.g., committing uncommitted changes before
releasing), follow the conventions in
.claude/commands/commit.md— in particular: no co-author lines, no Claude attribution, clean conventional commit format
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 · 61 lines · 70 tokens per session scan A 40cdaa613940
release is a skill published in the GitHub repository AI-Riksarkivet/ra-mcp (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 70 tokens to every session and 684 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
unity-release-readiness
Use before shipping a Unity build: version, build scenes, broken refs, assembly cycles, large assets, changelog, and package health.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
release-notes
Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.