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-nftgit 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-nft)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/node-kernel-nft"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/node-kernel-nft.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.02496 |
| Opus 5 | $0.00005 | $0.01248 |
| Sonnet 5 | $0.00002 | $0.00499 |
| Haiku 4.5 | $0.00001 | $0.00250 |
Grade A, and why
node-kernel-nft 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
openshift:node-kernel-nft
Synopsis
/openshift:node-kernel-nft <node> <image> --command <cmd> [--family <family>]
Description
The openshift:node-kernel-nft command allows interaction with the kernel to list packet filtering and classification rules managed by nftables. Nftables is the modern successor to iptables, providing a more unified and efficient packet filtering framework in the Linux kernel.
In OVN-Kubernetes environments, nftables may be used for:
- Modern packet filtering replacing legacy iptables
- Service load balancing rules
- Network policy enforcement
- NAT rules for ingress and egress traffic
- More efficient rule matching than iptables
The command uses oc debug to create an ephemeral container with host network access, then executes nft operations. The image must contain the nft CLI utility.
Implementation
This command invokes the openshift-node-kernel skill which provides kernel-level nftables inspection capabilities:
- Parameter Validation: Validates required node, image, and command parameters
- Utility Check: Verifies the debug image contains the
nftutility - Command Execution: Uses
oc debugto create ephemeral container and execute nft commands - Output Filtering: Removes common oc debug warnings to provide clean output
Skill Reference:
- Implementation:
extensions/openshift/skills/openshift-node-kernel/node-kernel-nft.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 nftables configuration 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
nftutility - 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 · 327 lines · 11 tokens per session scan A 39b0e51bca53
node-kernel-nft 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 2,496 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
web3-audit
Smart contract security audit — runs through 10 bug class checklist (accounting desync, access control, incomplete path, off-by-one, oracle errors, ERC4626, reentrancy, flash loan, signature replay, proxy/upgrade). Applies pre-dive kill signals first. Generates Foundry PoC template for confirmed findings. Usage…
gen
Automatically generates type definitions based on your Postgres database schema.
bmad-party-mode
Orchestrates lively group discussions between installed BMAD agents or custom personas, and helps author custom parties. Use when the user requests party mode, a roundtable, or multiple agent perspectives — or wants to create/configure a party, define personas, or build an AI focus-group panel.
tdd
TDD workflow - red-green-refactor per docs/methodology/tdd.md. Use when asked to '/tdd', 'TDD workflow', 'red-green-refactor', 'test-first development', 'write the failing test first'.
task
Delegate a task to Gemini CLI as a background or foreground job.
a
Quick alias for /analyze.