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/wangke19/gemini-ai-helpers/add-debug-waitgit 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-debug-wait)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/add-debug-wait"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/add-debug-wait.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.00012 | $0.04305 |
| Opus 5 | $0.00006 | $0.02152 |
| Sonnet 5 | $0.00002 | $0.00861 |
| Haiku 4.5 | $0.00001 | $0.00430 |
Grade A, and why
add-debug-wait 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.
How it starts
The opening of the file, as written. The whole thing — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:add-debug-wait
Synopsis
/ci:add-debug-wait <workflow-or-job-name> [timeout]
Description
The ci:add-debug-wait command adds a wait step to a CI job/workflow for debugging test failures.
What it does:
- Takes job name, OCP version, and optional timeout as input
- Finds and edits the job config or workflow file
- Adds
- ref: waitbefore the last test step (with optional timeout configuration) - Commits and pushes the change
- Gives you a GitHub link to create the PR
That's it! Simple, fast, and automated.
Implementation
The command performs the following steps:
Step 1: Gather Required Information
Prompt user for (in this order):
-
Workflow/Job Name: (from command argument $1 or prompt)
Workflow or job name: <user-input> Example: aws-c2s-ipi-disc-priv-fips-f7 Example: baremetalds-two-node-arbiter-e2e-openshift-test-private-tests -
Timeout (optional, from command argument $2):
Wait timeout in hours (optional, default: 3h): Examples: "1h", "2h", "8h", "24h", "72h" Valid range: 1h to 72h- If not provided, uses the wait step's default behavior (3 hours)
- Format: Integer followed by 'h' (e.g., "1h", "2h", "8h")
- Valid range: 1h to 72h (maximum enforced by wait step's timeout setting)
- Will be normalized to Go duration format (e.g., "8h" → "8h0m0s")
- This will be set as the
timeout:property on the wait step in the workflow/job YAML
-
OCP Version: (prompt - REQUIRED for searching job configs)
OCP version for debugging (e.g., 4.18, 4.19, 4.20, 4.21, 4.22):This is used to:
- Search the correct job config file (e.g., release-4.21)
- Document which version needs debugging
- Add context to the PR
-
OpenShift Release Repo Path: (prompt if not in current directory)
Path to openshift/release repository: Default: ~/repos/openshift-release
Step 2: Validate Environment
Silently validate (no user prompts):
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 · 624 lines · 12 tokens per session scan A 840456e36504
add-debug-wait is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 4,305 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-08-31.
Other commands, from other repositories
release
This document describes the standard release process for agtrace.
login
Connect the Supabase CLI to your Supabase account by logging in with your personal access token.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
pipeline-spec
Generate a CI/CD pipeline specification for a game project.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.