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/create)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/create"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/create/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/create"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/create.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.00020 | $0.06329 |
| Opus 5 | $0.00010 | $0.03164 |
| Sonnet 5 | $0.00004 | $0.01266 |
| Haiku 4.5 | $0.00002 | $0.00633 |
Grade A, and why
create 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 — 779 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:create
Synopsis
/jira:create <type> [project-key] <summary> [options]
Description
The jira:create command creates Jira issues following best practices and team-specific conventions. It supports creating stories, epics, features, tasks, bugs, and feature requests with intelligent defaults, interactive prompts, and validation.
This command is particularly useful for:
- Creating well-formed user stories with acceptance criteria
- Organizing epics and features with proper hierarchy
- Submitting bugs with complete reproduction steps
- Capturing customer-driven feature requests with business justification
- Maintaining consistency across team Jira practices
Key Features
- Multi-Type Support - Create stories, epics, features, tasks, bugs, or feature requests from a single command
- Smart Defaults - Automatically applies project-specific conventions (e.g., CNTRLPLANE, OCPBUGS, RFE)
- Interactive Guidance - Prompts for missing information with helpful templates
- Context Detection - Analyzes summary text to suggest components (ARO, ROSA, HyperShift)
- Security Validation - Scans for credentials and secrets before submission
- Template Support - Provides user story templates, bug report templates, feature request workflows, acceptance criteria formats
Issue Hierarchy and Parent Linking
Jira issues form a hierarchy. Understanding this hierarchy is critical for proper parent linking:
Feature (Strategic objective, market problem)
│
└── Epic (Body of work, fits in a quarter)
│
├── Story (User-facing functionality, fits in a sprint)
│
└── Task (Technical work, fits in a sprint)
Parent Linking Field Reference
CRITICAL: Different relationships use different Jira fields. Using the wrong field will cause creation to fail.
| Relationship | Field | MCP Parameter | Value Format |
|---|---|---|---|
| Epic → Feature | Parent Link (custom field) | additional_fields.customfield_10018 |
"PROJ-123" (string) |
| Story → Epic | Epic Link (custom field) | additional_fields.customfield_10014 |
"PROJ-123" (string) |
| Task → Epic | Epic Link (custom field) | additional_fields.customfield_10014 |
"PROJ-123" (string) |
| Task → Story | Epic Link (custom field) | additional_fields.customfield_10014 |
"PROJ-123" (string) |
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 · 779 lines · 20 tokens per session scan A 018571a38e39
create is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 6,329 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
projects
Provides tools for creating and managing your Supabase projects.
session-list
List recent sessions from the project ledger and offer to view one.
7a_stakeholder_comms
Generate stakeholder-facing communications: release notes, demo scripts, and change briefs.
convert-to-plan
Convert planning artifacts (lite-plan, workflow session, markdown) to issue solutions.
execute
Execute queue with DAG-based parallel orchestration (one commit per solution).
queue
Form execution queue from bound solutions using issue-queue-agent (solution-level).