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.
npx skills add beingmartinbmc/jambavan --skill release-checkergit clone --depth 1 https://github.com/beingmartinbmc/jambavanWrote 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/beingmartinbmc/jambavan/release-checker)<a href="https://agentmods.dev/skills/beingmartinbmc/jambavan/release-checker"><img src="https://agentmods.dev/badge/skills/beingmartinbmc/jambavan/release-checker/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/beingmartinbmc/jambavan/release-checker"><img src="https://agentmods.dev/badge/skills/beingmartinbmc/jambavan/release-checker.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.00048 | $0.00648 |
| Opus 5 | $0.00024 | $0.00324 |
| Sonnet 5 | $0.00010 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
release-checker 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 9d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Checker
If the verify_gate MCP tool is available, call it with your claim (and type: tests/build/fix/requirements/general) and use its output as a verification checklist. Otherwise, follow the protocol below directly.
Evidence rule
Match each completion claim to fresh evidence from the current working tree. If a relevant check is unavailable, unsafe, or disproportionate, report that limitation instead of presenting the result as verified.
The Gate
Before making a success or completion claim:
- IDENTIFY: What command proves this claim?
- RUN: Execute the smallest complete command appropriate to the risk.
- READ: Inspect the complete result, including exit code and failure count.
- VERIFY: Does output confirm the claim?
- YES → State the claim with concise evidence.
- NO → State the actual status and the relevant failure.
Do not imply that an unrun check passed.
Verification by claim type
Tests — Run the relevant test command and report its pass/fail summary. Claim the full suite passes only after running the full suite; a focused test proves only its own scope.
Build — Run the build command. Check exit code. "Build succeeds" requires build output showing exit 0. Linter passing ≠ build passing. Type-check passing ≠ bundle succeeding.
Bug fix — Prefer a reproducer that fails before the fix and passes after it. When a safe pre-fix run is impractical, explain the alternative evidence. Run regression checks in proportion to the change's blast radius.
Requirements met — Re-read the original requirements/plan. Create a line-by-line checklist. For each item: what proves it's done (test? output? demo?). Check each item with evidence. Report gaps honestly — "tests pass" ≠ "requirements met."
Release / PR ready — Apply the relevant checks above, inspect the final diff for scope and debug artifacts, and distinguish intended uncommitted work from unrelated user changes.
Unsupported-claim indicators
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.
- 9d ago First seen · 52 lines · 48 tokens per session scan A f77f2b2be8fe
release-checker is a skill published in the GitHub repository beingmartinbmc/jambavan (2 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 648 once invoked, about $0.0002 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-31.
Other skills, from other repositories
public-artifact-runtime-smoke-gate
Verify Python packages, CLIs, MCP servers, and Agent plugins through the exact installed artifact and real runtime contract. Use when source tests pass but a published release may omit modules, expose broken entry points, depend on local paths, fail without optional credentials, or behave differently after public…
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
verify-and-ship
Run all quality checks (tests, lint, typecheck), fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
ship-workflow
Automated release pipeline: merges main, runs tests, pre-landing review, version bump, changelog, bisectable commits, and PR creation. Triggers on: "ship it", "release this", "prepare for release", "open a PR", "push and PR", "land this", "/ship-workflow".
branch_health
Quick health check -- test counts and file stats for AIPass branches.