debug

Install

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.

agentmods

npx agentmods add commands/wangke19/gemini-ai-helpers/debug

Clone the repo

git clone --depth 1 https://github.com/wangke19/gemini-ai-helpers

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/debug.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/debug)

Your own site

<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/debug"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/debug.svg" alt="Measured on agentmods" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,098 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin unknown No closer match found in the catalogue.

Token cost

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.00013	$0.02098
Opus 5	$0.00006	$0.01049
Sonnet 5	$0.00003	$0.00420
Haiku 4.5	$0.00001	$0.00210

Measured today against content hash 5f329377ea08, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debug 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 today.

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.

extensions/olm/commands/debug.md · 219 lines

How it starts

The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Name

olm:debug

Synopsis

/olm:debug <issue-description> <must-gather-path> [olm-version]

Description

The olm:debug command analyzes OLM (Operator Lifecycle Manager) issues by correlating must-gather logs with the appropriate OLM source code. It automatically determines the OCP version from the must-gather logs, checks out the corresponding branch from the relevant OLM repositories, queries Jira for known bugs in the OCPBUGS project (OLM component), and provides detailed analysis and debugging insights.

Arguments

$1 (required): Issue description - A brief description of the OLM issue being investigated
$2 (required): Must-gather path - Absolute or relative path to the must-gather log directory
$3 (optional): OLM version - Either olmv0 (default) or olmv1
- olmv0: Uses operator-framework-olm repository
- olmv1: Uses operator-framework-operator-controller and cluster-olm-operator repositories

Implementation

Phase 1: Environment Setup and Validation

Validate arguments
- Check that issue description is provided
- Verify must-gather path exists and is accessible
- Set OLM version to olmv0 if not specified
Parse must-gather logs to determine OCP version
- Look for version information in must-gather logs
- Common locations:
  - cluster-scoped-resources/core/nodes/*.yaml - check node annotations
  - cluster-scoped-resources/config.openshift.io/clusterversions/*.yaml
- Extract OCP version (e.g., 4.14, 4.15, 4.16)
- Determine corresponding branch name (e.g., release-4.14)
Create working directory
- Use .work/olm-debug/<timestamp>/ for temporary files
- Create subdirectories: repos/, analysis/, logs/

Phase 2: Repository Setup

Clone appropriate repositories based on OLM version

For olmv0:
- Clone https://github.com/openshift/operator-framework-olm.git
- Checkout branch release-<ocp-version> (e.g., release-4.14)
- If branch doesn't exist, try main or master branch

Read the full file on GitHub · 219 lines

Changes

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.

today First seen · 219 lines · 13 tokens per session scan A 5f329377ea08

Subscribe to this mod's changes

debug is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 2,098 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-09-03.

Debugging extentions gemini-cli openshift redhat

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Name

Synopsis

Description

Arguments

Implementation

Phase 1: Environment Setup and Validation

Phase 2: Repository Setup

What this file has done since we first saw it

Other commands, from other repositories

spec-design

claude-request

release-prod

go

modernize-extract-rules

mem-search