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 generate-enhancementgit 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/generate-enhancement)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/generate-enhancement"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/generate-enhancement/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/generate-enhancement"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/generate-enhancement.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.09373 |
| Opus 5 | $0.00008 | $0.04686 |
| Sonnet 5 | $0.00003 | $0.01875 |
| Haiku 4.5 | $0.00002 | $0.00937 |
Grade C, and why
generate-enhancement scanned grade C with 2 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 7d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
if section and '<!-- MANUAL' in section: return True # Check for sync-exclude in frontmatter frontmatter = extract_frontmatter(enhancement) if frontmatter: sync_exclude = frontmatter.get('sync-exclude', []) if section_na Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -u "$USERNAME:$API_TOKEN" \ Copies of this mod
1 near-identical copy found in the catalogue:
- Generate Enhancement from Jira Epic or Feature — 91% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Enhancement from Jira Epic or Feature
This skill provides implementation guidance for generating OpenShift enhancement proposal markdown files based on Jira epic or feature issues.
When to Use This Skill
This skill is automatically invoked by the /jira:generate-enhancement command to guide the enhancement generation process from Jira epics or features.
Prerequisites
- MCP Jira server configured and accessible (or direct API access)
- User has permissions to view the target epic or feature
- Epic or Feature issue exists and has substantive content
- Understanding of OpenShift enhancement process
Reference Documentation:
What is an OpenShift Enhancement?
An OpenShift enhancement proposal is:
- A design document that describes significant changes to OpenShift
- A communication tool for building consensus among stakeholders
- An architectural record for future reference
- A mandatory process for all enhancements (starting with release 4.3)
Enhancement Template Structure
The enhancement proposal uses YAML frontmatter metadata and structured markdown sections:
---
title: neat-enhancement-idea
authors:
- "@github-username"
reviewers:
- "@reviewer1"
- "@reviewer2"
approvers:
- "@approver"
api-approvers:
- None # Or "@api-approver" if API changes
creation-date: yyyy-mm-dd
last-updated: yyyy-mm-dd
status: provisional
tracking-link:
- https://issues.redhat.com/browse/FEATURE-123
---
# Enhancement Title
## Summary
## Motivation
### User Stories
### Goals
### Non-Goals
## Proposal
### Workflow Description
### API Extensions
### Topology Considerations
#### Hypershift / Hosted Control Planes
#### Standalone Clusters
#### Single-node Deployments or MicroShift
#### OpenShift Kubernetes Engine
### Implementation Details/Notes/Constraints
### Risks and Mitigations
### Drawbacks
## Alternatives (Not Implemented)
## Open Questions [optional]
## Test Plan
## Graduation Criteria
### Dev Preview -> Tech Preview
### Tech Preview -> GA
### Removing a deprecated feature
## Upgrade / Downgrade Strategy
## Version Skew Strategy
## Operational Aspects of API Extensions
## Support Procedures
## Infrastructure Needed [optional]
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.
- 7d ago First seen · 1,436 lines · 16 tokens per session scan C 957b9782213f
generate-enhancement is a skill published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 9,373 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (hidden instructions, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
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…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.