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-aipcc-creategit 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-aipcc-create)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/jira-aipcc-create"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-aipcc-create/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-aipcc-create"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/jira-aipcc-create.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.00052 | $0.01223 |
| Opus 5 | $0.00026 | $0.00611 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
jira-aipcc-create 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create AIPCC Jira Issue
Create Jira issues in the AIPCC project using the acli CLI.
Prerequisites
aclimust be installed and authenticated (acli jira auth)
Implementation
Step 1: Infer Issue Details from Context
Analyze the conversation to determine:
-
Summary: A concise title (under 100 characters) describing the issue
-
Description: A Markdown description with relevant context, root cause, fix details, or requirements (use Markdown)
-
Type: One of the following based on the nature of work
Bug: problem that impairs or prevents product functions; tracks escaped defectsStory: action-oriented, smallest unit of work that can be completed within one sprintEpic: large user story that needs to be broken down; groups bugs, stories, and tasks to show progress of a larger effort; represents significant deliverable; does not span teamsFeature: use when tracking capability or well-defined set of functionality delivering business value; can include additions/changes to existing functionalitySpike: time-bound unit of work representing research-related task; not easy to sizeInitiative: use when capturing internal improvementsTask: unit of work to be accomplished, not end-user facing
-
Component: One of the valid AIPCC components:
Accelerator EnablementAI Eng AgilistAI Testing + Workflow ValidationAIPCC EcosystemsAIPCC ProductizationDevelopment PlatformModel ValidationPyTorchWheel Package Index
-
Parent Epic (optional): If the user specifies an epic key (e.g. AIPCC-1234), include it as the parent
If any field cannot be confidently inferred, ask the user.
Step 2: Confirm with the User
Present the proposed issue details to the user in a clear format:
I'll create the following AIPCC JIRA issue:
**Type**: Bug
**Component**: Wheel Package Index
**Parent Epic**: AIPCC-1234 (if specified)
**Summary**: Fix duplicate CI pipeline runs
**Description**:
> [description]
Shall I go ahead and create this?
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 · 160 lines · 52 tokens per session scan A a505318d38b8
jira-aipcc-create is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 5d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,223 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…