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-automation/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-automation)<a href="https://agentmods.dev/skills/agigante80/actual-mcp-server/release-automation"><img src="https://agentmods.dev/badge/skills/agigante80/actual-mcp-server/release-automation/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-automation"><img src="https://agentmods.dev/badge/skills/agigante80/actual-mcp-server/release-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Prompt Injection · line 6 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Agent Snooping · line 10 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00136 | $0.03187 |
| Opus 5 | $0.00068 | $0.01594 |
| Sonnet 5 | $0.00027 | $0.00637 |
| Haiku 4.5 | $0.00014 | $0.00319 |
Grade A, and why
release-automation 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 12d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release automation
Make the missing release impossible. The release skill (.claude/skills/release/SKILL.md) is
the invoked ship someone runs; this is the unattended layer that runs without being invoked,
so a promotion to main with no version bump is blocked (or, for verified dependency
updates, auto-bumped), never silently shipped. In this repo the layer is already partly
installed: a local release-gate hook plus two auto-release workflows. This skill documents how
the pieces compose and how to maintain them.
Composition, not duplication. Semver rules and the version source live in the
releaseskill and the version-marker section ofCLAUDE.md(canonicalVERSIONfile, mirrors managed byscripts/version-bump.js). This skill enforces them, it does not restate them.
The one mechanism: VERSION vs latest tag
All lanes share a single primitive: compare the working-tree VERSION against the latest
released vX.Y.Z tag (not the previous commit; the tag is the only truth for "what is
released") and act on one verdict:
| Verdict | Meaning | What a lane does with it |
|---|---|---|
first-release |
no release tag yet | allow (historical only; this repo has tags since v0.x) |
ahead |
VERSION > latest tag, already bumped deliberately |
ship as-is, never re-bump |
equal |
VERSION == latest tag, nobody bumped |
the lane's policy decides (block, or auto-patch) |
behind |
VERSION < latest tag, branch is stale |
hard stop (regression) |
The ahead/behind handling is the load-bearing part: it is what stops a naive "always patch on
merge" from double-bumping a deliberate 0.8.0 into 0.8.1, and what refuses to publish a
regression. In this repo the primitive is implemented twice, single-sourced by intent:
scripts/version-bump.js(the write path): before any bump it runs the production-tag freshness check (git ls-remote --tags origin) and aborts onbehind. This is the guard against the parallel-bump pattern (the scheduled auto-release ships while a local branch is unsynced). Recovery:git fetch origin && git merge origin/main. Override only with--force, and only when production is genuinely wrong; therelease-manageragent requires explicit user confirmation first.npm run version:check(scripts/version-check.js, the read path): verifies the canonicalVERSIONand its mirrors (package.json, doc**Version:**markers, container labels) agree, so the verdict is computed over one value, not several drifting ones. It runs in the Validate job of.github/workflows/ci-cd.ymland in pre-commit; drift fails closed. If it fails,npm run version:bump -- syncre-syncs mirrors without bumping.
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.
- 12d ago First seen · 189 lines · 136 tokens per session scan A 60697bf42b16
release-automation is a skill published in the GitHub repository agigante80/actual-mcp-server (54 stars, last pushed yesterday), licensed MIT. It adds 136 tokens to every session and 3,187 once invoked, about $0.0007 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
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ai-agents-generation-and-release
Operate the ai-agents generation and release machinery, covering the seven buildall.py generators, generateagents.py, syncpluginlib.py, the drift gates, the version-free plugin manifests, and the npm publish path. Use when you say regenerate the mirrors, run the drift checks, why is the plugin version gate red…
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.