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 openshift-eng/ai-helpers --skill add-jira-triage-linkgit clone --depth 1 https://github.com/openshift-eng/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/openshift-eng/ai-helpers/add-jira-triage-link)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/add-jira-triage-link"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/add-jira-triage-link/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/openshift-eng/ai-helpers/add-jira-triage-link"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/add-jira-triage-link.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.00023 | $0.00756 |
| Opus 5 | $0.00012 | $0.00378 |
| Sonnet 5 | $0.00005 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
add-jira-triage-link 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add JIRA Triage Link
This skill adds a Component Readiness triage record link to a JIRA issue description so that anyone viewing the bug can monitor the on-going status of all regressions triaged to it.
When to Use This Skill
Use this skill after creating or updating a triage record via the triage-regression skill. The link gives bug viewers a way to see all regressions associated with the bug in Component Readiness.
Prerequisites
- JIRA_USERNAME and JIRA_API_TOKEN environment variables must be set
- Python 3.6+
Implementation Steps
Step 1: Run the Script
script_path="plugins/ci/skills/add-jira-triage-link/add_jira_triage_link.py"
python3 "$script_path" OCPBUGS-12345 \
--triage-id 456 \
--format json
Arguments:
issue_key: JIRA issue key (e.g., OCPBUGS-12345)
Required Options:
--triage-id <id>: Triage record ID from Component Readiness
Options:
--format json|text: Output format (default: text)
Step 2: Parse the Output
output=$(python3 "$script_path" OCPBUGS-12345 --triage-id 456 --format json)
success=$(echo "$output" | jq -r '.success')
if [ "$success" = "true" ]; then
already=$(echo "$output" | jq -r '.already_present')
if [ "$already" = "true" ]; then
echo "Triage link already in description"
else
echo "Triage link added"
fi
fi
Script Output Format
JSON Format (--format json)
Success (link added):
{
"success": true,
"issue_key": "OCPBUGS-12345",
"triage_url": "https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/triages/456",
"already_present": false
}
Success (link already present):
{
"success": true,
"issue_key": "OCPBUGS-12345",
"triage_url": "https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/triages/456",
"already_present": true
}
Error:
{
"success": false,
"error": "Failed to update description: HTTP 403: ...",
"issue_key": "OCPBUGS-12345"
}
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 · 101 lines · 23 tokens per session scan A 81b39e73f974
add-jira-triage-link is a skill published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 756 once invoked, about $0.0001 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.