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 opendatahub-io/ai-helpers --skill jira-workitem-viewgit clone --depth 1 https://github.com/opendatahub-io/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/opendatahub-io/ai-helpers/jira-workitem-view)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/jira-workitem-view"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-workitem-view/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-workitem-view"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-workitem-view.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.00039 | $0.01356 |
| Opus 5 | $0.00019 | $0.00678 |
| Sonnet 5 | $0.00008 | $0.00271 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
jira-workitem-view 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Workitem View
Retrieve and display comprehensive details of a Jira ticket using the acli CLI.
Prerequisites
aclimust be installed and authenticated (acli jira auth)
Implementation
Step 1: Verify ACLi Setup
Before proceeding, verify that acli is installed and authenticated by invoking the acli-setup-check skill:
/acli-setup-check
If the setup check fails, stop execution and guide the user to fix the issue.
Step 2: Determine Ticket Key
- If a ticket key is provided by the user (e.g., "AIPCC-1234"), use it
- Otherwise, search the conversation history for Jira ticket references matching the pattern
[A-Z]+-\d+ - If no ticket is found, ask the user: "Which Jira ticket would you like to view?"
Step 3: Fetch Full Ticket Details
Execute the command to retrieve all ticket fields:
Fetch ticket details with validated key
acli jira workitem view "$TICKET_KEY" --fields '*all' --json
This returns a comprehensive JSON object containing all ticket fields, custom fields, and metadata.
### Step 4: Parse and Format Output
Parse the JSON output and extract the following fields for display:
#### Core Fields
- **Key**: Issue key (e.g., AIPCC-1234)
- **Summary**: Issue title
- **Type**: Issue type (Bug, Story, Epic, Feature, etc.)
- **Status**: Current status (To Do, In Progress, Done, etc.)
- **Priority**: Priority level
- **Project**: Project key and name
#### People
- **Assignee**: Current assignee (or "Unassigned")
- **Reporter**: Person who created the ticket
- **Creator**: Original creator (if different from reporter)
#### Dates
- **Created**: Creation timestamp
- **Updated**: Last update timestamp
- **Due Date**: Due date (if set)
- **Resolution Date**: When the ticket was resolved (if resolved)
#### Content
- **Description**: Convert from Atlassian Document Format (ADF) to plain text if needed. Display the first 500 characters with option to show full text.
- **Labels**: List of labels
- **Components**: List of components
- **Fix Version**: Target version (if set)
#### AIPCC Custom Fields (if applicable)
- **Status Summary** (customfield_10814): Leadership status update
- **Color Status** (customfield_10712): Red/Yellow/Green health indicator
#### Relationships
- **Parent**: Parent epic or feature (if set)
- **Child Issues**: Count and list of child issues
- **Links**: Related tickets (blocks, is blocked by, relates to, etc.)
- **Subtasks**: List of subtasks
#### Recent Activity
- **Last 3-5 Comments**: Show the most recent comments with author and timestamp
### Step 5: Display Results
Present the parsed information in a structured, human-readable format:
=== AIPCC-1234: Fix duplicate CI pipeline runs ===
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 · 179 lines · 39 tokens per session scan A 8788e6c5bc4f
jira-workitem-view is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 5d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,356 once invoked, about $0.0002 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…