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/analyze-cve)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/analyze-cve"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/analyze-cve/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/openshift-eng/ai-helpers/analyze-cve"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/analyze-cve.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.00011 | $0.11926 |
| Opus 5.5 | $0.00004 | $0.04770 |
| Sonnet 5.5 | $0.00002 | $0.02385 |
| Haiku 4.5 | $0.00001 | $0.01193 |
Grade E, and why
analyze-cve scanned grade E with 4 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- `graphviz` for visual call graph generation (`brew install graphviz` or `sudo apt-get install graphviz`) Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- The same rule applies to SSH keys, `~/.netrc` contents, Git credential helpers, and any secrets mounted as files. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "${RELEASE_CLONE_DIR}" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- When logging command invocations for debugging, **mask** credential arguments. Pass auth headers via a `chmod 600` curl config file (`curl -K`) — never as a `-H "Authorization: ..."` argv flag, which exposes the token Copies of this mod
1 near-identical copy found in the catalogue:
- analyze-cve — 100% identical, 606 lines differ
How it starts
The opening of the file, as written. The whole thing — 706 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
compliance:analyze-cve
Synopsis
/compliance:analyze-cve <CVE-ID> [--repo=<url-or-component>] [--algo=vta|rta|cha|static] [--auto-approve=yes|no]
/compliance:analyze-cve --jira=<PROJ-NNN> [--repo=...] [--algo=...] [--auto-approve=yes|no]
/compliance:analyze-cve --jql="<JQL query>" [--repo=...] [--algo=...] [--auto-approve=yes|no]
Description
The compliance:analyze-cve command performs comprehensive security vulnerability analysis for Go projects. Given a CVE identifier — supplied directly, or resolved from a Jira ticket — it resolves and clones the affected repository, gathers vulnerability intelligence, analyzes the codebase for impact, generates a risk report, optionally applies fixes, and optionally opens a GitHub pull request after a verified fix.
Repository resolution works in four ways, in priority order: (1) an explicit --repo= (full URL or short image/component name), (2) exactly one pre-cloned repository already present in this workspace's repos/ directory when --repo= was not passed, (3) an image name extracted from a Jira ticket's summary/labels/custom fields when --jira=/--jql= was used, or (4) an interactive prompt for the repository URL or image name. See Phase 0.7 for the full resolution and cloning logic.
Designed for both interactive use and headless execution (e.g. claude --print "/compliance:analyze-cve --jira=OCPBUGS-12345 --auto-approve=yes") for scheduled/periodic runs.
Arguments
Exactly one of the following input modes is required:
<CVE-ID>— Direct CVE identifier (format:CVE-YYYY-NNNNN, case-insensitive). Use when you already know the CVE.--jira=PROJ-NNN— Jira ticket key (e.g.--jira=OCPBUGS-12345). The command fetches the ticket and extracts the CVE ID, affected image name, and enrichment context (CVSS, CWE, priority, workarounds) from it.--jql="..."— JQL query (e.g.--jql="project = OCPBUGS AND labels = needs-cve-analysis"). The command fetches a batch of matching issues, filters out any already labeledai-cve-analyzed, and processes exactly one of the remainder per run (see Phase 0.3). Re-running the same JQL periodically works through the queue over multiple invocations.
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 Changed · +526 lines scan B → E 57b59172724d
- 1mo ago First seen · 180 lines · 11 tokens per session scan B 0da631d39b38
analyze-cve is a command published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 11,926 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it E with 4 findings (asks for root, reaches for credential files, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
check-go
Run Go code quality checks including formatting, linting, vetting, and tests.
skill-go-gin-api
Padrões DARE para APIs REST em Go + Gin (ou stdlib net/http) + sqlc + PostgreSQL. Handlers, services, repositories, middleware, validador, JWT, rate limit, swag OpenAPI.
go-test
A Go testing command that follows test-driven development, or TDD: write a failing test, implement the smallest change that passes it, then improve the code.
go-review
Go code review for idiomatic patterns.
gopher-fix
Lightweight Go bug fix: reproduce with failing test → diagnose root cause → apply minimal fix → quality gates → review.
trex.verify
Run all static analysis checks: go vet, format verification, and linting.