Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/voodootikigod/skills-checkWrote 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/commands/voodootikigod/skills-check/release)<a href="https://agentmods.dev/commands/voodootikigod/skills-check/release"><img src="https://agentmods.dev/badge/commands/voodootikigod/skills-check/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/commands/voodootikigod/skills-check/release"><img src="https://agentmods.dev/badge/commands/voodootikigod/skills-check/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.00000 | $0.00404 |
| Opus 5.5 | $0.00000 | $0.00162 |
| Sonnet 5.5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 1mo 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.
What it actually says
Release a new version of skills-check.
Arguments
- $ARGUMENTS: Version bump type — "patch", "minor", or "major". Defaults to "minor" if not specified.
Steps
-
Determine the new version. Read the current version from
packages/cli/package.json. Apply the requested semver bump ($ARGUMENTS, default "minor") to compute the new version number. -
Verify preconditions:
- Working tree is clean (
git status --porcelainis empty) - On the
mainbranch - Up to date with remote (
git pull --dry-runshows no changes) - All tests pass (
npm test) - Build succeeds (
npm run build)
- Working tree is clean (
-
Bump version in ALL package.json files (must stay in lock step):
package.json(root)packages/cli/package.jsonpackages/schema/package.jsonpackages/web/package.json
-
Commit the version bump:
chore: bump version to X.Y.Z -
Create the version tag:
vX.Y.Z -
Push commit and tag:
git push origin main git push origin vX.Y.Z -
Update the floating major version tag (e.g.,
v1for any1.x.xrelease):git tag -f vMAJOR git push origin vMAJOR --forceThis ensures users referencing
voodootikigod/skills-check@v1in GitHub Actions get the latest release. -
Confirm completion. Print a summary of:
- Previous version → new version
- Tag created
- Floating tag updated
- Remind that
publish.ymlwill handle npm publish automatically from the new tag
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.
- 1mo ago First seen · 49 lines · 0 tokens per session scan A 40e8b97b432c
release is a command published in the GitHub repository voodootikigod/skills-check (14 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 404 tokens. 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 commands, from other repositories
release
Verify, write the CHANGELOG, cut a version — then hand the release sequence back.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
vios-release-note
Generate a complete VIOS multi-arch release note for a given build drop version. Fetches container images from GitLab compose.env, GitLab commit titles since the previous release tag, Jira VST tickets, NVBugs entries, Slack channel evidence, and Outlook email evidence, then renders and saves a formatted release note.
release-update
(dev-only) release-update maintainer harness — Claude Code upstream change tracker (release-notes version-delta sweep + docs sync). NOT distributed to user projects.