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/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/analyze-performance)<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.
<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>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.00013 | $0.04790 |
| Opus 5 | $0.00006 | $0.02395 |
| Sonnet 5 | $0.00003 | $0.00958 |
| Haiku 4.5 | $0.00001 | $0.00479 |
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.
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.
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:
-
OpenShift CLI (oc)
- Install from: https://mirror.openshift.com/pub/openshift-v4/clients/ocp/
- Verify with:
oc version
-
Active cluster connection
- Must be connected to an OpenShift cluster
- Verify with:
oc whoami
-
Cluster admin permissions
- Required to access etcd pods and metrics
- Verify with:
oc auth can-i get pods -n openshift-etcd
-
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 15for 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)..."
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.
- 9d ago First seen · 603 lines · 13 tokens per session scan A 7530e6beaa86
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.
Other commands, from other repositories
10_gofer_cloud
Deploy and configure the Gofer cloud integration for remote pipeline execution.
create-docker-mcp-tunnel
Stand up an Google MCP tunnel locally with Docker Compose so Gemini can call a private MCP server (manual-credentials quickstart).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.