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/implementgit 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/implement)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/implement"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/implement.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.00043 | $0.00607 |
| Opus 5 | $0.00022 | $0.00303 |
| Sonnet 5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
implement 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
openshift-tls-profile:implement
Synopsis
/openshift-tls-profile:implement [question or implementation request]
Description
The openshift-tls-profile:implement command provides guidance on implementing TLS security profiles for operators and workloads running on OpenShift. It helps with:
- Recommended: Using
github.com/openshift/controller-runtime-common/pkg/tlsfor controller-runtime operators (providesFetchAPIServerTLSProfile,NewTLSConfigFromProfile, andSecurityProfileWatcher) - Reading TLS configuration from the APIServer custom resource
- Converting OpenShift TLS profiles to Go
crypto/tlsconfiguration - Applying TLS settings to Kubernetes operator webhook servers, metrics endpoints, HTTP/gRPC clients and servers
- Using
github.com/openshift/library-go/pkg/cryptoutilities for cipher suite conversion - Using the library-go configobserver pattern with
ObserveTLSSecurityProfilefor OpenShift operators - Handling TLS profile changes with graceful restart (recommended over hot-reload)
Implementation
- Read the skill documentation from
extensions/openshift-tls-profile/skills/openshift-tls-profile/SKILL.md - Based on the user's question or request, provide specific guidance from the skill
- Include relevant code examples and implementation patterns
- Reference OpenShift documentation and API types as needed
Arguments
- $1: Optional question or implementation request. If not provided, displays an overview of the skill capabilities.
Return Value
- Format: Guidance and code examples for implementing TLS security profiles
Examples
-
Get overview of TLS profile implementation:
/openshift-tls-profile:implement -
Ask about reading TLS profile from cluster:
/openshift-tls-profile:implement How do I read the TLS profile from the APIServer CR? -
Get help with gRPC server configuration:
/openshift-tls-profile:implement Show me how to configure a gRPC server with the TLS profile
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 · 74 lines · 43 tokens per session scan A e469a1e2f8ff
implement is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 607 once invoked, about $0.0002 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).