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/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/validate-blockers)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/validate-blockers"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/validate-blockers/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/wangke19/gemini-ai-helpers/validate-blockers"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/validate-blockers.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.00012 | $0.01647 |
| Opus 5 | $0.00006 | $0.00823 |
| Sonnet 5 | $0.00002 | $0.00329 |
| Haiku 4.5 | $0.00001 | $0.00165 |
Grade A, and why
validate-blockers 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.
This is a copy
100% identical to validate-blockers — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:validate-blockers
Synopsis
/jira:validate-blockers [target-version] [component-filter] [--bug issue-key]
Note: target-version is required unless --bug is provided.
Description
The jira:validate-blockers command helps release managers make data-driven decisions on proposed release blockers. It analyzes bugs with "Release Blocker = Proposed" status using Red Hat OpenShift release blocker criteria and provides clear APPROVE/REJECT/DISCUSS recommendations with detailed justification.
This command is essential for:
- Validating proposed release blockers
- Making blocker approval/rejection decisions
- Understanding why a bug should or shouldn't block a release
- Reviewing blocker criteria compliance
Key Features
- Proposed Blocker Focus – Automatically filters for bugs with Release Blocker = Proposed
- Red Hat OpenShift Release Blocker Criteria – Analyzes against documented blocker criteria
- Clear Recommendations – Provides APPROVE, REJECT, or DISCUSS recommendations
- Detailed Justification – Shows which criteria matched and analysis rationale
- Component Filtering – Scope validation to specific components
Implementation
For detailed implementation guidance including JQL queries, scoring algorithms, and decision logic, see the jira-validate-blockers skill.
High-Level Workflow
- Parse Arguments and Build Filters – Extract arguments (target version, component filter, bug ID). Build JQL query for:
- Single bug mode (if --bug provided): Query specific bug by issue key (version not required)
- Component + version mode (if both provided): Query proposed blockers matching target version and component, excluding already-fixed bugs (status not in Closed, Release Pending, Verified, ON_QA)
- Version only mode (if version provided): Query all proposed blockers for target version, excluding already-fixed bugs
- Error: If neither --bug nor version provided, show error message
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 · 198 lines · 12 tokens per session scan A 349c90cfe571
validate-blockers is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,647 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to validate-blockers, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
fix
Revision workflow for bug fixes and feedback-driven changes.
session-list
List recent sessions from the project ledger and offer to view one.
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
gofer_hydrate
Reverse-engineer specification from existing code (Hydration).
fix
Diagnose and fix bugs, errors, and issues in code.
debug-with-file
Interactive hypothesis-driven debugging with documented exploration, understanding evolution, and Gemini-assisted correction.