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/wangke19/gemini-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/wangke19/gemini-ai-helpers/add-enhancement)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/add-enhancement"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/add-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/commands/wangke19/gemini-ai-helpers/add-enhancement"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/add-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.00007 | $0.02777 |
| Opus 5 | $0.00003 | $0.01388 |
| Sonnet 5 | $0.00001 | $0.00555 |
| Haiku 4.5 | $0.00001 | $0.00278 |
Grade A, and why
add-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 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.
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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
openshift:add-enhancement
Synopsis
/openshift:add-enhancement [area] <name> <description> <jira>
Description
The openshift:add-enhancement command creates a new OpenShift Enhancement
Proposal (EP) based on the official template from the openshift/enhancements
repository. It generates a comprehensive enhancement document with all required
sections, metadata, and guidance following OpenShift's enhancement process.
This command automates the creation of enhancement proposals by:
- Fetching the latest enhancement template from the openshift/enhancements repository
- Analyzing the provided description to extract what, why, and who information
- Generating user stories, goals, and non-goals based on the requirements
- Creating properly formatted enhancement files with all required sections
- Applying OpenShift-specific conventions for feature gates, API design, and testing requirements
Arguments
- area (optional): Enhancement area (subdirectory under enhancements/). If not provided, the command will attempt to infer the best area from the enhancement description and ask for confirmation.
- name: One-line title describing the enhancement
- description: Detailed description (what, why, who)
- jira: JIRA ticket URL for tracking
Implementation
Act as an experienced software architect to create a comprehensive enhancement proposal. Follow these steps:
Important: Reference the guidance in the OpenShift enhancements repository at https://github.com/openshift/enhancements/blob/master/dev-guide/feature-zero-to-hero.md, particularly the section "Writing an OpenShift Enhancement", when creating enhancement proposals. This guide provides essential context on the OpenShift Enhancement Proposal process, feature gates, API design conventions, testing requirements, and promotion criteria.
- Verify Repository: Before proceeding, ensure you are operating in the correct repository:
- Check if the current directory is a git repository:
git rev-parse --is-inside-work-tree - Verify the repository is openshift/enhancements or a fork:
- Get the remote URL:
git config --get remote.origin.url - Check if the URL contains "openshift/enhancements" (e.g.,
[email protected]:openshift/enhancements.gitorhttps://github.com/openshift/enhancements.git) - For forks, the URL might be different (e.g.,
[email protected]:username/enhancements.git) - in this case, check if it's a fork by examining the repository structure (presence ofenhancements/directory andguidelines/directory with enhancement_template.md)
- Get the remote URL:
- If verification fails, exit with a clear error message: "Error: This command must be run in the openshift/enhancements repository or a fork. Please clone the repository first or navigate to the correct directory."
- If successful, continue to the next step
- Check if the current directory is a git repository:
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 · 143 lines · 7 tokens per session scan A f1a2327c18e8
add-enhancement is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 2,777 once invoked, about $0.0000 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
5_gofer_implement
Execute all tasks from tasks.md phase by phase with feedback loops and engineering review.
eai-update
Use this command to install or update EAI Gofer for the current AI coding app. This command works without an EAI project, a Gofer scaffold, or EAI sign-in.
modernize-extract-rules
Mine business logic from legacy code into testable, human-readable rule specifications.
mem-search
Full-text search in the memory vault (archives, contexts, histories, index).
help
Get help with the hookify plugin.
checklist
Generate a custom checklist for the current feature based on user requirements.