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/ovs-db)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/ovs-db"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/ovs-db/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/ovs-db"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/ovs-db.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.03483 |
| Opus 5 | $0.00006 | $0.01741 |
| Sonnet 5 | $0.00003 | $0.00697 |
| Haiku 4.5 | $0.00001 | $0.00348 |
Grade B, and why
ovs-db scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Fedora/RHEL: `sudo dnf install openvswitch` How it starts
The opening of the file, as written. The whole thing — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
sosreport:ovs-db
Synopsis
/sosreport:ovs-db [sosreport-path] [--db] [--flows-only] [--query <json>]
Description
The ovs-db command analyzes Open vSwitch data collected in sosreports. It operates in four modes:
- Default mode: Full analysis - conf.db + all text files (requires ovsdb-tool)
- Database mode (
--db): Database only - analyze conf.db (requires ovsdb-tool) - Text files mode (
--flows-only): Text files only - no ovsdb-tool needed! - Query mode (
--query): Run custom OVSDB JSON queries (requires ovsdb-tool)
What it analyzes:
From Database (Default or --db Mode)
- System Information: OVS version, DPDK settings, external IDs (from conf.db)
- Bridge Details: Datapath type (kernel/userspace), fail mode, ports (from conf.db)
- Interface Inventory: By type, with pod-to-interface mapping (from conf.db)
From Text Files (Default or --flows-only Mode)
- System Information: OVS version, DPDK settings, external IDs (from
ovs-vsctl list Open_vSwitch) - Topology: Bridges with ports grouped by type (from
ovs-vsctl show) - Bridge Details: Datapath type, fail mode, CT zones (from
ovs-vsctl list bridge) - Interface Inventory: By type, with pod-to-interface mapping (from
ovs-vsctl list interface) - OpenFlow Flows: Flow counts, drop detection, top flows (from
ovs-ofctl dump-flows) - Port Statistics: RX/TX drops and errors (from
ovs-ofctl dump-ports) - Tunnel Ports: Configured tunnels (from
ovs-appctl tnl.ports.show) - Datapath Health: Flow table usage vs limit (from
ovs-appctl upcall.show) - OVS Internal Stats: Netlink, OpenFlow, OVSDB counters (from
ovs-appctl coverage.show)
Custom Queries (--query Mode)
- Direct OVSDB table queries (requires ovsdb-tool)
Modes of operation:
- Default: Full analysis - conf.db + all text files (requires ovsdb-tool, falls back to text files if not available)
- Database (
--db): Database only - analyze conf.db (requires ovsdb-tool) - Text Files (
--flows-only): Text files only - no ovsdb-tool needed - Query Mode (
--query): Run custom OVSDB JSON queries (requires ovsdb-tool)
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 · 392 lines · 13 tokens per session scan B b9d49bf9c197
ovs-db 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 3,483 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
la
A command for capturing and decoding signals with a Saleae logic analyzer, a device that records electrical digital signals over time. It supports buses such as UART, SPI, and I2C, which are common ways chips communicate with peripherals.
fix
Diagnose and fix bugs, errors, and issues in code.
issue:discover
Discover potential issues from multiple perspectives (bug, UX, test, quality, security, performance, maintainability, best-practices) using CLI explore. Supports Exa external research for security and best-practices perspectives.
debug-with-file
Interactive hypothesis-driven debugging with documented exploration, understanding evolution, and Gemini-assisted correction.
mqtt-debug
A command for debugging MQTT, a messaging protocol commonly used by connected devices and services. It covers publishing messages, monitoring subscriptions, and checking connections.
seed-snapshot
Take a cognitive snapshot — current Seed mind state for debugging or analysis.