Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Borda/AI-Rignpx agentmods add skills/borda/ai-rig/rig-releaseWrote 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/borda/ai-rig/rig-release)<a href="https://agentmods.dev/skills/borda/ai-rig/rig-release"><img src="https://agentmods.dev/badge/skills/borda/ai-rig/rig-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/borda/ai-rig/rig-release"><img src="https://agentmods.dev/badge/skills/borda/ai-rig/rig-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.00034 | $0.00721 |
| Opus 5.5 | $0.00014 | $0.00288 |
| Sonnet 5.5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
Rig 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 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.
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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rig Release
Read Evidence rules.
This workflow never publishes, tags, pushes, or mutates a remote. Publication stays human-owned.
Workflow
- Read the baseline from HEAD. Do not use an uncommitted version. For this plugin family,
package.jsonis the version manifest; confirm the repository's policy for the package being released. - Classify the change. Fix or wording: patch. New capability or surface: minor. Breaking contract: major, and only with explicit approval.
- Start the run.
rig_evidencewithaction: "start",skill: "rig-release", and the package root. - Run the full gate set.
rig_gatewithaction: "run"and no name filter. A single failure blocks readiness; do not retry unchanged. - Synchronize documentation. Verify the changelog bullet describes user-visible impact, the README version marker matches the manifest, and changed agents, skills, tools, and commands are documented.
- Draft the release pack. Bind the commit range with
rig_evidenceaction: "record"andcommit, then produce the three drafts below from that evidence. Every line must trace to a commit, finding, or changelog entry; an empty section is better than an invented one. - Verify the package. Run the package build or
npm pack --dry-run(or the project equivalent) and check the file list. No tests, plans, credentials, or private evidence may ship. - Compare versions. Declared version must equal
HEADplus exactly one SemVer step unless the package is new. Record the comparison. - Finalize. Produce a readiness verdict with blockers, the drafts, and a human checklist.
Release pack
- Release notes. Group by Added, Changed, Fixed, Security, Deprecated, and Removed. Each entry names the user-visible effect, not the internal refactor, and credits the contributor when the commit or issue records one.
- Migration notes. List breaking changes, renamed options, changed defaults, and required user actions, each with before/after snippets and a rollback path. Say explicitly when no action is required.
- Contributor replies. Draft a short factual reply per linked issue or pull request: what shipped, what did not, and what happens next. Never promise a date, never claim a fix that is not in the range, and never post it.
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 First seen · 41 lines · 34 tokens per session scan A e85a35bdaf02
Rig Release is a skill published in the GitHub repository Borda/AI-Rig (29 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 721 once invoked, about $0.0001 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-28.
Other skills, from other repositories
version-release
Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.
release-guard
Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
git-workflow
A Git workflow guide for organizing commits, branches, pull requests, releases, and automated version-control tasks. Git is the system developers use to track code changes and collaborate.
git-publish-release
A release assistant for GitHub, a service for hosting software projects. It compares project history and creates a GitHub Release with notes for a chosen version tag.
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.