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/opendatahub-io/ai-helpersnpx agentmods add skills/opendatahub-io/ai-helpers/jira-status-summaryWrote 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/opendatahub-io/ai-helpers/jira-status-summary)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/jira-status-summary"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-status-summary/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/opendatahub-io/ai-helpers/jira-status-summary"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-status-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00061 | $0.01631 |
| Opus 5 | $0.00030 | $0.00816 |
| Sonnet 5 | $0.00012 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
jira-status-summary 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 12d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Status Summary
Update the "Status Summary" and "Color Status" fields on an AIPCC Feature or Initiative ticket with an AI-generated summary and health color.
Prerequisites
- Python 3 and
uvmust be installed and available in PATH aclimust be installed and authenticated (acli jira auth)JIRA_API_TOKENenvironment variable must be set with a valid API token for https://redhat.atlassian.netJIRA_EMAILenvironment variable must be set with the email address associated with your Atlassian account- The
jira-activityskill must be installed (provides child ticket activity data)
Usage
This skill takes a single ticket key as input and writes a formatted status summary to the Jira "Status Summary" field and sets the "Color Status" dropdown.
If the user asks for a dry run (or uses the words "dry run", "preview",
"don't write", "show me first"), add --dry-run to the write command in
Step 5. This prints the formatted summary without writing to Jira, so the
user can review before committing.
Implementation
Step 1: Determine the Ticket Key
- If a ticket key is provided by the user, use it
- Otherwise, search the conversation history for JIRA ticket references matching the pattern
[A-Z]+-\d+ - If no ticket is found in context, ask the user: "Which ticket should I update the Status Summary for? (e.g., AIPCC-1234)"
Step 2: Fetch Previous Status Summary and Color Status
Fetch the previous Status Summary and Color Status from the ticket:
acli jira workitem view <TICKET-KEY> -f 'customfield_10814,customfield_10712' --json
Parse the JSON output to extract:
customfield_10814: the previous summary (rich-text / ADF content)customfield_10712: the previous color status ("Green", "Yellow", or "Red")
If either field is empty or unset, treat it as no previous value. Save both outputs for use in Step 4 -- the previous color provides trending context (e.g. improving from red to yellow).
If the command fails (e.g., due to permissions or network issues), continue with Step 3 and generate the summary without prior context.
What ships with it
1 file 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.
- 12d ago First seen · 184 lines · 61 tokens per session scan A 2650da0e980c
jira-status-summary is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 5d ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,631 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…