Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpersnpx agentmods add commands/wangke19/gemini-ai-helpers/health-check-jirasWrote 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/health-check-jiras)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/health-check-jiras"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/health-check-jiras/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/health-check-jiras"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/health-check-jiras.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.00014 | $0.03056 |
| Opus 5 | $0.00007 | $0.01528 |
| Sonnet 5 | $0.00003 | $0.00611 |
| Haiku 4.5 | $0.00001 | $0.00306 |
Grade A, and why
health-check-jiras 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
teams:health-check-jiras
Synopsis
/teams:health-check-jiras --project <project> [--component comp1 comp2 ...] [--status status1 status2 ...] [--include-closed] [--limit N]
/teams:health-check-jiras --project <project> --team <team-name> [--status status1 status2 ...] [--include-closed] [--limit N]
Description
The teams:health-check-jiras command queries JIRA bugs for a specified project and generates summary statistics. It leverages the list-jiras command to fetch raw JIRA data and then calculates counts by status, priority, and component to help understand the bug backlog at a glance.
By default, the command includes:
- All currently open bugs
- Bugs closed in the last 30 days (to track recent closure activity)
This command is useful for:
- Getting a quick count of open bugs in a JIRA project
- Analyzing bug distribution by status, priority, or component
- Tracking recent bug flow (opened vs closed in last 30 days)
- Generating summary reports for bug backlog
- Monitoring bug velocity and closure rates by component or team
- Comparing bug counts across different components
- Getting team-level bug summaries across all team components
Implementation
-
Verify Prerequisites: Check that Python 3 is installed
- Run:
python3 --version - Verify version 3.6 or later is available
- Run:
-
Verify Environment Variables: Ensure JIRA authentication is configured
-
Check that the following environment variables are set:
JIRA_URL: Base URL for JIRA instance (e.g., "https://redhat.atlassian.net")JIRA_USERNAME: Your JIRA username (email address) for Basic authJIRA_API_TOKEN: Your JIRA API token
-
Verify with:
echo "JIRA_URL: ${JIRA_URL}" echo "JIRA_USERNAME: ${JIRA_USERNAME}" echo "JIRA_API_TOKEN: ${JIRA_API_TOKEN:+***set***}" -
If missing, guide the user to set them:
export JIRA_URL="https://redhat.atlassian.net" export JIRA_USERNAME="[email protected]" export JIRA_API_TOKEN="your-api-token-here"
-
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 · 341 lines · 14 tokens per session scan A 35f5e7f5695a
health-check-jiras is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 3,056 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).