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 commands/dmzoneill/redhat-ai-workflow/deploy-ephemeralgit clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflowWrote 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/dmzoneill/redhat-ai-workflow/deploy-ephemeral)<a href="https://agentmods.dev/commands/dmzoneill/redhat-ai-workflow/deploy-ephemeral"><img src="https://agentmods.dev/badge/commands/dmzoneill/redhat-ai-workflow/deploy-ephemeral.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 | $0.00000 | $0.00317 |
| Opus 5 | $0.00000 | $0.00159 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade C, and why
deploy-ephemeral scanned grade C with 1 finding 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.
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.
- Uses `KUBECONFIG=~/.kube/config.e` (never copies kubeconfig!) What it actually says
/deploy-ephemeral
Deploy an MR or branch to an ephemeral environment.
Overview
Deploy an MR or branch to an ephemeral environment.
Arguments
No arguments required.
Usage
Process Flow
flowchart TD
START([Start]) --> PROCESS[Process Command]
PROCESS --> END([Complete])
style START fill:#6366f1,stroke:#4f46e5,color:#fff
style END fill:#10b981,stroke:#059669,color:#fff
Details
Prerequisites
- Load DevOps persona:
persona_load("devops") - Be logged into ephemeral cluster
- Have the MR ID or branch name
How to Use
Tell me:
- "Deploy MR 1459 to ephemeral"
- "Test AAP-61214 in ephemeral"
- "Deploy my branch to ephemeral"
I will:
- Get the full commit SHA from GitLab
- Verify image exists in Quay (Konflux build)
- Reserve an ephemeral namespace
- Deploy using bonfire with correct ClowdApp (main or billing)
- Wait for pods to be ready
- Report deployment status
Important
- Uses
KUBECONFIG=~/.kube/config.e(never copies kubeconfig!) - Image tag must be 64-char SHA256 digest
- Template ref must be 40-char git SHA
Related Commands
(To be determined based on command relationships)
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 · 57 lines · 0 tokens per session scan C 60ec9f891c0c
deploy-ephemeral is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 317 tokens. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
pr-address
Address PR review comments on current branch.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
spec-research
需求 → 约束集（并行探索 + OPSX 提案）.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.