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/node-kernel-ipgit 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/node-kernel-ip)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/node-kernel-ip"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/node-kernel-ip.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.00011 | $0.03548 |
| Opus 5 | $0.00005 | $0.01774 |
| Sonnet 5 | $0.00002 | $0.00710 |
| Haiku 4.5 | $0.00001 | $0.00355 |
Grade A, and why
node-kernel-ip 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.
How it starts
The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
openshift:node-kernel-ip
Synopsis
/openshift:node-kernel-ip <node> <image> --command <cmd> [--options <opts>] [--filter <params>]
Description
The openshift:node-kernel-ip command allows interaction with the kernel to list routing tables, network devices, and interfaces. The ip utility is the modern Linux networking configuration tool that shows and manipulates routing, network devices, policy routing, and tunnels.
In OVN-Kubernetes environments, the ip command is essential for:
- Inspecting OVN overlay network interfaces (genev_sys_*, ovn-k8s-mp0, etc.)
- Viewing routing tables for pod and service traffic
- Debugging network namespace configurations
- Analyzing interface states and configurations
- Troubleshooting connectivity issues between nodes and pods
The command uses oc debug to create an ephemeral container with host network access, then executes ip operations. The image must contain the ip utility (from iproute2 package).
Implementation
This command invokes the openshift-node-kernel skill which provides kernel-level networking inspection capabilities:
- Parameter Validation: Validates required node, image, and command parameters
- Utility Check: Verifies the debug image contains the
iputility - Command Execution: Uses
oc debugto create ephemeral container and execute ip commands - Output Filtering: Removes common oc debug warnings to provide clean output
Skill Reference:
- Implementation:
extensions/openshift/skills/openshift-node-kernel/node-kernel-ip.sh - Helper functions:
extensions/openshift/skills/openshift-node-kernel/kernel-helper.sh - Documentation:
extensions/openshift/skills/openshift-node-kernel/SKILL.md
Parameters
Required Parameters
-
node: Name of the Kubernetes node where network information should be extracted.
- Must be a valid node name in the cluster
- Example:
ovn-control-plane,ovn-worker,worker-0
-
image: Container image to use for creating a debug connection to the node.
- Must contain
iputility (iproute2 package) - Common images:
registry.redhat.io/rhel9/support-toolsnicolaka/netshoot
- Must contain
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 · 352 lines · 11 tokens per session scan A bc6ac66822a7
node-kernel-ip is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 3,548 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.
Other commands, from other repositories
spec-design
Create comprehensive technical design for a specification.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.
release-prod
Guide you through promoting stage → production.
go
READY 작업을 현재 사용자의 명시적 요청으로 실행할 때 사용.
modernize-extract-rules
Mine business logic from legacy code into testable, human-readable rule specifications.
mem-search
Full-text search in the memory vault (archives, contexts, histories, index).