analyze-performance

analyze-performance is a command for Claude Code from wangke19/gemini-ai-helpers. It costs 13 tokens per session (4,790 once invoked), scanned A, a copy of analyze-performance, Apache-2.0.

A command that analyzes etcd performance. Etcd is the database that stores the state of a Kubernetes or OpenShift cluster.

In plain words
What is it for?
Use it to investigate latency, find disk or network bottlenecks, plan capacity, and tune an OpenShift cluster.
Why use it?
Slow disk or network operations in etcd can delay pod changes, cause API timeouts, and make the cluster feel unresponsive.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Good fit Use it to investigate latency, find disk or network bottlenecks, plan capacity, and tune an OpenShift cluster.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/wangke19/gemini-ai-helpers/analyze-performance
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.

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

Made for: Claude Code.

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.

agentmods badge for analyze-performance

README.md
[![agentmods](https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-performance/github.svg)](https://agentmods.dev/commands/wangke19/gemini-ai-helpers/analyze-performance)
Your own site
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/analyze-performance"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-performance/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.

agentmods 80×15 button for analyze-performance

Your own site · 80×15
<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/analyze-performance"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-performance.svg" alt="Reviewed on agentmods" width="80" 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 4,790 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.04790
Opus 5 $0.00006 $0.02395
Sonnet 5 $0.00003 $0.00958
Haiku 4.5 $0.00001 $0.00479

Measured 9d ago against content hash 7530e6beaa86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

analyze-performance 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 9d 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.

Origin

This is a copy

100% identical to analyze-performance — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

extensions/etcd/commands/analyze-performance.md · 603 lines

How it starts

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

Name

etcd:analyze-performance

Synopsis

/etcd:analyze-performance [--duration <minutes>]

Description

The analyze-performance command analyzes etcd performance metrics to identify latency issues, slow operations, and potential bottlenecks. It examines disk performance, commit latency, network latency, and provides recommendations for optimization.

Etcd performance is critical for cluster responsiveness. Slow etcd operations can cause:

  • API server timeouts
  • Slow pod creation and updates
  • Controller delays
  • Overall cluster sluggishness

This command is useful for:

  • Diagnosing slow cluster operations
  • Identifying disk I/O bottlenecks
  • Detecting network latency issues
  • Capacity planning
  • Performance tuning

Prerequisites

Before using this command, ensure you have:

  1. OpenShift CLI (oc)

  2. Active cluster connection

    • Must be connected to an OpenShift cluster
    • Verify with: oc whoami
  3. Cluster admin permissions

    • Required to access etcd pods and metrics
    • Verify with: oc auth can-i get pods -n openshift-etcd
  4. Running etcd pods

    • At least one etcd pod must be running
    • Check with: oc get pods -n openshift-etcd -l app=etcd

Arguments

  • --duration (optional): Duration in minutes to analyze logs (default: 5)
    • Analyzes recent logs for the specified duration
    • Longer durations provide more comprehensive analysis
    • Example: --duration 15 for 15-minute window

Implementation

The command performs the following analysis:

1. Verify Prerequisites

if ! command -v oc &> /dev/null; then
    echo "Error: oc CLI not found"
    exit 1
fi

if ! oc whoami &> /dev/null; then
    echo "Error: Not connected to cluster"
    exit 1
fi

# Parse duration argument (default: 5 minutes)
DURATION=5
if [[ "$1" == "--duration" ]] && [[ -n "$2" ]]; then
    DURATION=$2
fi

echo "Analyzing etcd performance (last $DURATION minutes)..."

Read the full file on GitHub · 603 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.

  1. 9d ago First seen · 603 lines · 13 tokens per session scan A 7530e6beaa86

Subscribe to this mod's changes

analyze-performance is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 4,790 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to analyze-performance, differing in 0 lines, and is treated as a copy.