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 agentmods add rules/openshift/hypershift/create-jira-itemsgit clone --depth 1 https://github.com/openshift/hypershiftWhat 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 | $0.00051 | $0.01266 |
| Opus 5 | $0.00026 | $0.00633 |
| Sonnet 5 | $0.00010 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
create-jira-items 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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General
You should try to use a Jira MCP server to create any Jira items or issues.
Any HyperShift feature, epic, story, or task should be created in the Jira project known as Red Hat OpenShift Control Planes also known as CNTRLPLANE.
Any request to make a bug ticket or make the content for a bug ticket should go under the Jira project known as OpenShift Bugs, also known as OCPBUGS.
Set the Jira component to:
- HyperShift / ARO - when the issue is about ARO HCP
- HyperShift / ROSA - when the issue is about ROSA HCP
- HyperShift - when it is not clear if the issue is about a particular HyperShift platform
When you create a Jira issue, add this label: ai-generated-jira.
By default, set the Security Level to the following: Red Hat Employee.
Never include credentials or secrets in any Jira issue (e.g., usernames/passwords, cloud keys, API tokens, kubeconfigs, SSH keys, certificates). This applies to descriptions, comments, attachments, screenshots, logs, and URLs. Redact before sharing.
Use Jira’s native description formatting (Wiki/ADF): headings, bullet lists, code blocks, and tables.
Standard Parts of a Jira Issue
Summary
A summary is a brief text synopsis of the issue.
It answers the questions - How do we typically refer to this issue?
A summary is needed for the following Jira issue types: Outcomes, Features, Initiatives, Epics, Stories, Spikes, Tasks, Bugs, Tickets, Risks, Sub-Tasks.
Setting Versions
For any Jira story or task, unless specified differently from the user, the target version (also known as customfield_12319940) should always be openshift-4.21.
For any OCPBUGS Jira issue, the affected version/s and target version (also known as customfield_12319940) fields should default to 4.21.
Never set the Fix Version/s or fixVersions fields.
Instructions on specific Jira Issue components
Creating a feature
TBD
Creating an epic
Summary: An agile epic is a body of work that can be broken down into specific items (called user stories) based on the needs/requests of customers or end-users. Epics are an important practice for agile and DevOps teams. When adopting agile and DevOps, an epic serves to manage work.
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.
- 2d ago First seen · 122 lines · 51 tokens per session scan A 916c6641bf4f
create-jira-items is a cursor rule published in the GitHub repository openshift/hypershift (538 stars, last pushed 2d ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,266 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.