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/inspect)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/inspect"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/inspect.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.1 | $0.00009 | $0.02950 |
| Opus 5 | $0.00005 | $0.01475 |
| Sonnet 5 | $0.00002 | $0.00590 |
| Haiku 4.5 | $0.00001 | $0.00295 |
Grade B, and why
inspect 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 3d 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.
- RHEL/Fedora: `sudo dnf install skopeo` How it starts
The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
container-image:inspect
Synopsis
/container-image:inspect <image>
Description
The container-image:inspect command provides a comprehensive breakdown of a container image using skopeo and podman. It analyzes the image metadata, configuration, and layers to give you detailed information about the image structure, size, architecture, and contents.
This command is useful for:
- Understanding image composition and layers
- Verifying image architecture and OS
- Checking image size and disk usage
- Inspecting image labels and annotations
- Validating image configuration
- Troubleshooting image-related issues
- Verifying multi-architecture image support
- Checking which platforms are available for an image
- Comparing platform-specific image differences
- Planning multi-arch image builds
The command works with images from any registry (quay.io, docker.io, registry.redhat.io, etc.) and automatically detects whether an image is a manifest list (multi-architecture) or a single image, providing detailed analysis for both cases.
Prerequisites
Required Tools:
-
skopeo - For image inspection without pulling
- Check if installed:
which skopeo - Installation:
- RHEL/Fedora:
sudo dnf install skopeo - Ubuntu/Debian:
sudo apt-get install skopeo - macOS:
brew install skopeo
- RHEL/Fedora:
- Documentation: https://github.com/containers/skopeo
- Check if installed:
-
podman (Optional) - For additional image analysis
- Check if installed:
which podman - Installation:
- RHEL/Fedora:
sudo dnf install podman - Ubuntu/Debian:
sudo apt-get install podman - macOS:
brew install podman
- RHEL/Fedora:
- Documentation: https://podman.io/
- Check if installed:
Registry Authentication:
For private registries, ensure you're authenticated:
# Using skopeo
skopeo login registry.example.com
# Using podman
podman login registry.example.com
Implementation
The command performs the following analysis steps:
- Check Tool Availability:
- Verify
skopeois installed - Check for
podman(optional but recommended) - If tools are missing, provide installation instructions
- Verify
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.
- 3d ago First seen · 316 lines · 9 tokens per session scan B 81c4af48deeb
inspect is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 2,950 once invoked, about $0.0000 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
start
Starts the Supabase local development stack.
stop
Stops the Supabase local development stack.
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).
ocean-stop
Gracefully stop the boil-ocean run and its scheduler.
sync-validate
Validate Claude MCP schema and target capability compatibility before syncing.
help
Get help with the hookify plugin.