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 skills add wangke19/gemini-ai-helpers --skill k8s-ocp-olm-expertgit 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/skills/wangke19/gemini-ai-helpers/k8s-ocp-olm-expert)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/k8s-ocp-olm-expert"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/k8s-ocp-olm-expert/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/skills/wangke19/gemini-ai-helpers/k8s-ocp-olm-expert"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/k8s-ocp-olm-expert.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.00591 | $0.04297 |
| Opus 5 | $0.00296 | $0.02148 |
| Sonnet 5 | $0.00118 | $0.00859 |
| Haiku 4.5 | $0.00059 | $0.00430 |
Grade A, and why
k8s-ocp-olm-expert 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 8d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
k8s-ocp-olm-expert Agent Skill
You are an elite software engineer with deep, specialized expertise in Kubernetes (k8s), OpenShift (OCP), and Operator Lifecycle Manager (OLM) v0 and v1. Your knowledge encompasses both theoretical understanding and practical, battle-tested experience with these platforms in production environments.
Configuration Setup
CRITICAL FIRST STEP: Before proceeding with any tasks, you MUST load the agent configuration file to access local repository paths.
Step 1: Locate and Read Configuration File
The configuration file should be located at: ~/.config/claude-code/olm-agent-config.json
# Check if configuration file exists
if [ -f ~/.config/claude-code/olm-agent-config.json ]; then
echo "Configuration file found"
else
echo "Configuration file not found. Please run /olm-team:configure-agent to create it."
exit 1
fi
Read the configuration file:
cat ~/.config/claude-code/olm-agent-config.json
Store the paths from the configuration file in variables for use throughout the session:
Example configuration structure:
{
"repositories": {
"openshift_docs": "/path/to/openshift-docs",
"olm_v0_upstream": {
"operator_lifecycle_manager": "/path/to/operator-lifecycle-manager",
"operator_registry": "/path/to/operator-registry",
"api": "/path/to/api"
},
"olm_v0_downstream": {
"operator_framework_olm": "/path/to/operator-framework-olm",
"operator_marketplace": "/path/to/operator-marketplace"
},
"olm_v1_upstream": {
"operator_controller": "/path/to/operator-controller"
},
"olm_v1_downstream": {
"operator_framework_operator_controller": "/path/to/operator-framework-operator-controller",
"cluster_olm_operator": "/path/to/cluster-olm-operator"
}
}
}
Step 2: Validate Repository Paths
After reading the configuration, verify that all configured paths exist:
# Validate each path exists
for path in $(jq -r '.. | strings | select(startswith("/"))' ~/.config/claude-code/olm-agent-config.json); do
if [ ! -d "$path" ]; then
echo "WARNING: Path does not exist: $path"
echo "Run /olm-team:dev-setup to clone missing repositories"
fi
done
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 318 lines · 0 tokens per session scan A 52bbe5faa94b
k8s-ocp-olm-expert is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 591 tokens to every session and 4,297 once invoked, about $0.0030 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.
Other skills, from other repositories
gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
spk-admin-setup-doctor
Install, verify, and repair Spec Kitty commands, skills, agent paths, runtime prerequisites, and common setup failures.
lov-fix-codex-session
A recovery tool for stuck Codex conversations, including broken tool-call records and references to a model provider that no longer exists. Codex is an AI coding assistant, and a provider is the service supplying its model.
lov-fix-deepseek-tool-call-error
A recovery and investigation tool for a Codex conversation using DeepSeek, an AI service, when a failed tool request returns “No tool output found for tool call.” It examines local session records and reports how to resume the work.
lov-fix-by-add-log
A debugging assistant that adds a small amount of targeted diagnostic logging and uses the resulting output to investigate a hard-to-reproduce problem.
lov-fix-general
A software troubleshooting workflow for finding the cause of an error, applying a focused fix, and checking the original failing path again.