Borrowing it
Nothing to install: this file belongs to agigante80/actual-mcp-server. 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/agigante80/actual-mcp-server/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/agigante80/actual-mcp-serverWrote 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/agigante80/actual-mcp-server/release)<a href="https://agentmods.dev/skills/agigante80/actual-mcp-server/release"><img src="https://agentmods.dev/badge/skills/agigante80/actual-mcp-server/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/agigante80/actual-mcp-server/release"><img src="https://agentmods.dev/badge/skills/agigante80/actual-mcp-server/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.00103 | $0.03145 |
| Opus 5 | $0.00051 | $0.01572 |
| Sonnet 5 | $0.00021 | $0.00629 |
| Haiku 4.5 | $0.00010 | $0.00314 |
Grade A, and why
release scanned grade A with 1 finding 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 yesterday.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
const { execSync } = require("child_process"); How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release (develop to main)
Promote the current develop to main as a versioned release, then close the
GitHub issues that release implemented. The implement-ticket pipeline stops at
develop on purpose; this skill is the explicit, human-triggered step that ships
develop to main and tidies the tracker so implemented tickets do not linger open.
The closing-tickets step is the reason this skill exists: without it, every ticket implemented since the last release stays open after shipping, and closing them by hand is easy to forget.
When this runs
Any request to release / merge develop to main. Optional argument: an expected
version (e.g. 0.6.40) to assert against the VERSION on develop as a safety
check. Everything is on main and the tag; develop is the source.
No em or en dashes anywhere (CLAUDE.md hard rule). Honest reporting: never claim released until the release pipeline is green.
Version sources (single source of truth + mirrors)
The canonical version is the VERSION file. Everything else is a mirror that
must be kept equal to it: package.json version, the doc **Version:**
markers, and container labels. scripts/version-bump.js propagates the bump to
all mirrors; scripts/version-check.js (run as npm run version:check) fails
if any mirror disagrees, and runs in the Validate CI workflow and pre-commit
so drift is caught before release, not during it.
Bump modes (semver)
| Mode | Effect |
|---|---|
patch / minor / major |
npm run version:bump -- <level>: bump VERSION, propagate to all mirrors, sync doc markers |
sync |
npm run version:bump -- sync: do NOT bump; only re-sync mirrors + doc markers to the current VERSION (fixes drift) |
The bump level is a human judgement; never auto-infer it. Operator contract:
breaking the deployment is major, an opt-in feature is minor, a fix / CVE /
dependency update is patch. Bumping is a single committed step
(chore(release): bump version to X.Y.Z) on develop BEFORE the release runs
(implement-ticket normally does this).
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.
- yesterday Changed · +16 lines 010ca2c4abe2
- 9d ago First seen · 246 lines · 103 tokens per session scan A eb2937b728ce
release is a skill published in the GitHub repository agigante80/actual-mcp-server (51 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 3,145 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
updater_guide
Guidance for checking for and installing Row-Bot updates.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.