Voiden is an offline API workspace that stores requests, tests, documentation, and reusable API components in plain-text Markdown-based files managed with Git. Developers, QA engineers, and technical writers use it to build, test, document, script, and collaborate on APIs.
Borrowing it
Nothing to install: this file belongs to VoidenHQ/voiden. 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/VoidenHQ/voiden/main/.agents/skills/plugin-release-check/SKILL.mdgit clone --depth 1 https://github.com/VoidenHQ/voidenWrote 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/voidenhq/voiden/plugin-release-check)<a href="https://agentmods.dev/skills/voidenhq/voiden/plugin-release-check"><img src="https://agentmods.dev/badge/skills/voidenhq/voiden/plugin-release-check/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/voidenhq/voiden/plugin-release-check"><img src="https://agentmods.dev/badge/skills/voidenhq/voiden/plugin-release-check.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.00071 | $0.00805 |
| Opus 5.5 | $0.00028 | $0.00322 |
| Sonnet 5.5 | $0.00014 | $0.00161 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
plugin-release-check 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 27d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin release / registry consistency check
Each directory under plugins/<name>/ is its own independent git repo (its
own GitHub remote, its own versioning, its own release cycle) — separate from
the main Voiden app. The central source of truth for what's actually
installable is plugins/plugin-registry/extensions.json, one object per
plugin, keyed by id, with at least repo (owner/name), version, and
voidenVersion.
These three numbers can drift out of sync:
plugins/<name>/package.json→version(local working tree)- The plugin repo's latest GitHub release tag
plugins/plugin-registry/extensions.json→ that plugin's"version"field
How to check
For each plugin directory with a package.json and a git remote (skip
plugin-registry itself):
# 1. Local version
node -p "require('./plugins/<name>/package.json').version"
# 2. Repo remote -> owner/name
git -C plugins/<name> remote get-url origin # https://github.com/<owner>/<repo>.git
# 3. Latest GitHub release tag for that repo
gh release view --repo <owner>/<repo> --json tagName -q .tagName
# 4. Registry's recorded version for that plugin id
# (read plugins/plugin-registry/extensions.json, find the matching "id")
Strip the leading v from the release tag before comparing against semver
in package.json.
Decision tree per plugin
-
local version > latest release tag → the working tree has unreleased changes. Ask the user to cut a new GitHub release (with the built runner/asset, matching how existing releases for that repo are structured) for that plugin — do not create the release yourself, this is a user-confirmed action. Mention that
extensions.jsonwill also need itsversion(andvoidenVersion, if the plugin's minimum Voiden version requirement changed) updated to match once the release exists. -
local version == latest release tag, but registry version differs → the release exists but the registry hasn't caught up. Update
plugins/plugin-registry/extensions.jsonfor that plugin's entry:version(andvoidenVersionif it changed in this release) — bring it in sync with the actual release tag. This repo is also independent, so committing/pushing there needs the same confirmation as any other push.
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.
- 27d ago First seen · 75 lines · 71 tokens per session scan A 014e5f78819d
plugin-release-check is a skill published in the GitHub repository VoidenHQ/voiden (1,867 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 805 once invoked, about $0.0003 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-09-23.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
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.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
skillshare-release
Prepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when explicitly authorized. Use when the user says "release", "prepare release", "cut a release", or asks to publish a new…
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…