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-attachgit 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-attach)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/jira-workitem-attach"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-workitem-attach/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-attach"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-workitem-attach.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.00033 | $0.01973 |
| Opus 5 | $0.00016 | $0.00986 |
| Sonnet 5 | $0.00007 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade A, and why
jira-workitem-attach 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 11d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Workitem Attach
Upload file attachments to Jira tickets using the Jira REST API (since acli does not support attachment uploads).
Prerequisites
aclimust be installed and authenticated (acli jira auth) to verify the upload- Python 3.10+ and
uvmust be installed JIRA_API_TOKENenvironment variable must be set with a valid API tokenJIRA_EMAILenvironment variable must be set with the email address associated with your Atlassian account
Security Note: The JIRA_API_TOKEN is sensitive and should be kept secure:
- Never log or echo the token value
- Avoid running debug commands that print environment variables
- The upload script handles the token securely via HTTPS
- Do not share logs or command output that may contain the token
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: Verify Environment Variables
Check that the required environment variables are set:
if [[ -z "$JIRA_API_TOKEN" || -z "$JIRA_EMAIL" ]]; then
echo "Error: JIRA_API_TOKEN and JIRA_EMAIL environment variables must be set"
exit 1
fi
If either variable is missing, inform the user:
JIRA_API_TOKEN and JIRA_EMAIL environment variables are required for uploading attachments.
To set them:
export JIRA_EMAIL="[email protected]"
export JIRA_API_TOKEN="your-api-token"
Get your API token from:
https://id.atlassian.com/manage-profile/security/api-tokens
Note: The Python upload script will also validate these variables, but checking early provides better user experience.
Step 3: Determine Ticket Key and File Path
- Ticket Key:
- If provided by user, use it
- Otherwise, search conversation history for ticket references matching the pattern
[A-Z]+-\d+ - If not found, ask: "Which ticket should I attach the file to?"
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.
- 11d ago First seen · 243 lines · 33 tokens per session scan A a65285aa259c
jira-workitem-attach is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 4d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,973 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…