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/hominhtuong/qa-claude-pluginsWrote 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/hominhtuong/qa-claude-plugins/release-gate)<a href="https://agentmods.dev/commands/hominhtuong/qa-claude-plugins/release-gate"><img src="https://agentmods.dev/badge/commands/hominhtuong/qa-claude-plugins/release-gate/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/hominhtuong/qa-claude-plugins/release-gate"><img src="https://agentmods.dev/badge/commands/hominhtuong/qa-claude-plugins/release-gate.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.00102 | $0.00933 |
| Opus 5.5 | $0.00041 | $0.00373 |
| Sonnet 5.5 | $0.00020 | $0.00187 |
| Haiku 4.5 | $0.00010 | $0.00093 |
Grade A, and why
release-gate 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 38 lines · 102 tokens per session scan A 074c52b2ef07
release-gate is a command published in the GitHub repository hominhtuong/qa-claude-plugins (2 stars, last pushed 4mo ago), with no licence file. It adds 102 tokens to every session and 933 once invoked, about $0.0004 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-08-31.
Other commands, from other repositories
speckit.spex.finish
Smoke test + squash + merge/keep (land the code on main).
wg-release
Manage versions and generate changelogs for the wicked-garden plugin.
4-close-project
Name: 4-close-project Purpose: Apply an OpenSpec change through TDD, verify it, prepare or update the PR, and leave archive for after merge.
release-check
Run the release-readiness umbrella + draft a tweet-length announcement.
explore-release
This legacy command is a rename notice only. Its workflow is now rpi-explore-release.
publish-gate
Pre-publish smoke verification — pack, install into a tmpdir, run the configured smoke command, assert expected output. Catches the "code worked locally but the published tarball is broken" class of bug.