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 jira-conventionsgit 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/jira-conventions)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/jira-conventions"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/jira-conventions/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/jira-conventions"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/jira-conventions.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.00032 | $0.00548 |
| Opus 5.5 | $0.00013 | $0.00219 |
| Sonnet 5.5 | $0.00006 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
jira-conventions 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 1mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Conventions Router
This skill routes to the correct project or team conventions based on the Jira project key, component, or keywords in the issue summary.
Routing Table
Match on project key, component, or summary keywords. Load the corresponding reference file.
By Project Key
| Project Key | Conventions | Reference |
|---|---|---|
| CNTRLPLANE | Red Hat OpenShift Control Planes — features, epics, stories, tasks | CNTRLPLANE conventions |
| OCPBUGS | OpenShift Bugs — bug reports only | OCPBUGS conventions |
| GCP | GCP Hosted Control Planes (Hypershift on GKE) — stories, epics, tasks, bugs, features | GCP HCP conventions |
By Team / Keywords
Detect these keywords in the issue summary, description, or component to layer team-specific conventions on top of project conventions:
| Keywords | Team Conventions | Reference |
|---|---|---|
| HyperShift, ARO HCP, ROSA HCP, hosted control plane | HyperShift team — component selection (HyperShift / ARO, HyperShift / ROSA, HyperShift) | HyperShift conventions |
| GCP HCP, Hypershift on GKE, GKE hosted control plane | GCP HCP team — GCP project conventions, team templates, sizing guide | GCP HCP conventions |
Layering Rules
- Project conventions are loaded first based on the project key
- Team conventions are layered on top when keywords match
- Both can apply simultaneously (e.g., CNTRLPLANE + HyperShift)
- If no project or team matches, skip this skill — the issue uses only type-specific guidance from the
createskill
How to Use
After identifying the matching conventions:
- Read the linked reference file(s)
- Apply project-specific custom fields, version handling, and component requirements
- Layer team-specific conventions if keywords match (component selection, labels, templates)
- Defer to the
createskill for issue-type guidance (story template, bug template, etc.)
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.
- 1mo ago First seen · 46 lines · 32 tokens per session scan A 8e9c43ef017c
jira-conventions is a skill published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 548 once invoked, about $0.0001 per session on Opus 5.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-09-05.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…