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.
git 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/commands/openshift-eng/ai-helpers/generate-enhancement)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/generate-enhancement"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/generate-enhancement.svg" alt="Measured on agentmods" height="20"></a>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.00012 | $0.01969 |
| Opus 5 | $0.00006 | $0.00984 |
| Sonnet 5 | $0.00002 | $0.00394 |
| Haiku 4.5 | $0.00001 | $0.00197 |
Grade A, and why
generate-enhancement 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- generate-enhancement — 98% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:generate-enhancement
Synopsis
/jira:generate-enhancement <issue-key>
Description
The jira:generate-enhancement command generates an OpenShift enhancement proposal markdown file based on a Jira epic or feature. It fetches the feature details, analyzes the content, and creates an enhancement document following the OpenShift enhancement template structure.
This command is particularly useful for:
- Converting strategic Jira features or epics into formal enhancement proposals
- Bootstrapping enhancement documents with epic/feature context
- Maintaining consistency between Jira planning and enhancement documentation
- Accelerating the enhancement proposal writing process
Key Features
- Automatic Feature Fetching - Retrieves feature details from Jira including description, epics, and context
- Template-Based Generation - Creates enhancement markdown following the official OpenShift template
- Content Mapping - Intelligently maps Jira feature fields to enhancement sections
- Epic Integration - Incorporates linked epics as implementation details
- Interactive Refinement - Prompts for missing information and clarifications
- File Naming - Generates appropriate filename based on feature summary
Workflow
The command follows these steps:
1. Fetch Jira Epic or Feature
- Retrieve epic/feature details using MCP Jira tools or REST API
- Extract summary, description, child issues, components, timeline
- Validate issue type (must be an Epic or Feature issue type)
2. Analyze Epic or Feature Content
- Parse description, goals, acceptance criteria
- Identify user stories and objectives
- Extract scope and child issues (epics, stories, tasks)
- Determine topology considerations from components
3. Generate Enhancement Sections
- Map Jira content to enhancement template sections
- Create initial draft with available information
- Identify gaps requiring user input
4. Interactive Refinement
- Prompt for technical implementation details
- Collect test plan information
- Define graduation criteria
- Gather operational considerations
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.
- 4d ago First seen · 270 lines · 12 tokens per session scan A 327d523e7aa0
generate-enhancement is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 3d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,969 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.