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.
npx skills add wangke19/gemini-ai-helpers --skill jira-issues-by-componentgit 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/skills/wangke19/gemini-ai-helpers/jira-issues-by-component)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/jira-issues-by-component"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/jira-issues-by-component/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/skills/wangke19/gemini-ai-helpers/jira-issues-by-component"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/jira-issues-by-component.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.00025 | $0.01532 |
| Opus 5 | $0.00013 | $0.00766 |
| Sonnet 5 | $0.00005 | $0.00306 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade B, and why
JIRA Issues by Component - Helper Skill scanned grade B with 2 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 8d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 ~/.jira-credentials Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Provides secure curl wrapper for the jira:issues-by-component command to prevent token exposure This is a copy
95% identical to jira-issues-by-component — 6 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JIRA Issues by Component - Helper Skill
This skill provides a secure curl wrapper script for the jira:issues-by-component command. The wrapper prevents JIRA authentication token exposure in process listings and command history.
When to Use This Skill
This skill is automatically used by the jira:issues-by-component command. You typically don't need to invoke it directly unless you're:
- Developing or testing JIRA API integrations
- Building custom JIRA scripts that need secure authentication
- Debugging JIRA API connectivity issues
Security Benefits
The jira_curl.sh wrapper script provides:
- Token Protection: Authentication tokens never appear in process listings (
ps aux) - History Safety: Tokens are not saved in shell history files
- Process Isolation: Token is read from environment variables inside the script
- Clean Interface: Same curl arguments you're already familiar with
Files
jira_curl.sh
Secure curl wrapper that automatically adds JIRA authentication headers.
Location: extensions/jira/skills/jira-issues-by-component/jira_curl.sh
Usage:
jira_curl.sh [curl arguments...]
Required Environment Variables:
JIRA_URL: JIRA instance URL (e.g.,https://redhat.atlassian.net)JIRA_API_TOKEN: Authentication tokenJIRA_USERNAME: Atlassian account email for Basic auth
Example:
# Set credentials
export JIRA_URL="https://redhat.atlassian.net"
export JIRA_API_TOKEN="your-token-here"
export JIRA_USERNAME="[email protected]"
# Use wrapper (token hidden from process list)
jira_curl.sh -s -X POST -d '{"jql":"project=OCPBUGS"}' https://redhat.atlassian.net/rest/api/3/search/jql
How It Works
- Environment Check: Validates that
JIRA_URLand authentication token are set - Token Selection: Uses
JIRA_API_TOKENfor Atlassian Cloud authentication - Header Injection: Constructs
Authorization: Basic <base64>header inside the script usingJIRA_USERNAMEandJIRA_API_TOKEN - Process Replacement: Uses
exec curlto replace the script process with curl - Clean Execution: Token never crosses process boundaries as a visible argument
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 208 lines · 25 tokens per session scan B 1b9996db2823
JIRA Issues by Component - Helper Skill is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,532 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). It is 95% identical to jira-issues-by-component, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
spk-run-verdict-capture
Set a Spec Kitty work-package review verdict through the deterministic event-log seam, so every agent harness records approve/reject the same way.
spk-team-sync
Operate Spec Kitty tracker sync (sync pull/sync push/sync run for local providers) and hosted SaaS-backed mission data.
spk-run-program-orchestrate
Orchestrate multi-repo, multi-mission Spec Kitty programs across dependencies, parallel agents, review gates, merge, and post-merge closeout.
spk-gate-retrospective
Create or verify Spec Kitty mission retrospectives after merge and surface process learnings without blocking completed work.
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
cc-skill-project-guidelines-example
Project Guidelines Skill (Example).