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/generate-test-plan)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/generate-test-plan"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/generate-test-plan/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/generate-test-plan"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/generate-test-plan.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.00008 | $0.01833 |
| Opus 5 | $0.00004 | $0.00916 |
| Sonnet 5 | $0.00002 | $0.00367 |
| Haiku 4.5 | $0.00001 | $0.00183 |
Grade A, and why
generate-test-plan scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- The command uses curl to fetch JIRA data via REST API: https://redhat.atlassian.net/rest/api/3/issue/{$1} How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:generate-test-plan
Synopsis
/jira:generate-test-plan [JIRA issue key] [GitHub PR URLs]
Description
The 'jira:generate-test-plan' command takes a JIRA issue key and optionally a list of PR URLs. It fetches the JIRA issue details, retrieves all related PRs (or uses the provided PR list), analyzes the changes, and generates a comprehensive manual testing guide.
JIRA Issue Test Guide Generator
Implementation
- The command uses curl to fetch JIRA data via REST API: https://redhat.atlassian.net/rest/api/3/issue/{$1}
- Uses WebFetch to extract PR links from JIRA issue if no PRs provided
- Uses
gh pr viewto fetch PR details for each PR - Analyzes changes across all PRs to understand implementation
- Generates comprehensive manual test scenarios
Process Flow:
-
JIRA Analysis: Fetch and parse JIRA issue details:
- Use curl to fetch JIRA issue data:
curl -s "https://redhat.atlassian.net/rest/api/3/issue/{$1}" - Parse JSON response to extract:
- Issue summary and description
- Context and acceptance criteria
- Steps to reproduce (for bugs)
- Expected vs actual behavior
- Extract issue type (Story, Bug, Task, etc.)
- Use curl to fetch JIRA issue data:
-
PR Discovery: Get list of PRs to analyze:
- If no PRs provided in arguments ($2, $3, etc. are empty):
- Use WebFetch on https://redhat.atlassian.net/browse/{$1}
- Extract all GitHub PR links from:
- "Issue Links" section
- "Development" section
- PR links in comments
- If PRs provided in arguments:
- Use only the PRs provided in $2, $3, $4, etc.
- Ignore any other PRs linked to the JIRA
- If no PRs provided in arguments ($2, $3, etc. are empty):
-
PR Analysis: For each PR, fetch and analyze:
- Use
gh pr view {PR_NUMBER} --repo <your repo> --json title,body,commits,files,labels - Extract:
- PR title and description
- Changed files and their diffs
- Commit messages
- PR status (merged, open, closed)
- Read changed files to understand implementation details
- Use Grep and Glob tools to:
- Find related test files
- Locate configuration or documentation
- Identify dependencies
- Use
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 · 187 lines · 8 tokens per session scan A 89f464e10b9c
generate-test-plan is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,833 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
release-check
Run the release-readiness umbrella + draft a tweet-length announcement.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
evaluate
Evaluate a skill across model tiers using blind testing.
quality-gate
Run technical quality checks before commits or PRs — build, types, lint, test, security, diff review.
validate
Command "validate" from Vimalk0703/shipworthy, covering /validate — pre-push validation gate, what this does, steps, when to run and output format.
speckit.git.remote
Detect Git remote URL for GitHub integration.