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/ask-sippy)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/ask-sippy"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/ask-sippy.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.00019 | $0.01350 |
| Opus 5 | $0.00010 | $0.00675 |
| Sonnet 5 | $0.00004 | $0.00270 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
ask-sippy scanned grade A 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. **API Request**: Sends a POST request to the Sippy API using the `oc-auth` skill's curl wrapper: This is a copy
91% identical to ask-sippy — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:ask-sippy
Synopsis
/ask-sippy [question]
Description
The ask-sippy command allows you to query the Sippy AI agent, which has deep knowledge about OpenShift CI infrastructure, including:
- CI payload status and rejection reasons
- Job failures and patterns
- Test results and trends
- Release quality metrics
- Historical CI data analysis
The command sends your question to the Sippy API and returns the agent's response. Note that complex queries may take some time to process as the agent analyzes CI data. Please inform the user of this.
Security
IMPORTANT SECURITY REQUIREMENTS:
Gemini is granted LIMITED and SPECIFIC access to the DPCR cluster token for the following AUTHORIZED operations ONLY:
- READ operations: Querying the Sippy API for CI data analysis
Gemini is EXPLICITLY PROHIBITED from:
- Modifying cluster resources (deployments, pods, services, etc.)
- Deleting or altering any data
- Accessing secrets, configmaps, or sensitive data beyond Sippy API responses
- Making any cluster modifications
- Using the token for any purpose other than the specific operations listed above
Token Usage:
The DPCR cluster token is used solely for authentication with the Sippy API. This token grants the same permissions as the authenticated user and must be handled with appropriate care. The curl_with_token.sh wrapper handles all authentication automatically.
Implementation
- Validate Arguments: Checks that a question was provided
- Notify User: Informs the user that the query is being processed (may take time)
- API Request: Sends a POST request to the Sippy API using the
oc-authskill's curl wrapper:# Use curl_with_token.sh from oc-auth skill - it automatically adds the OAuth token # DPCR cluster API: https://api.cr.j7t7.p1.openshiftapps.com:6443 curl_with_token.sh https://api.cr.j7t7.p1.openshiftapps.com:6443 -s -X POST "https://sippy-auth.dptools.openshift.org/api/chat" \ -H "Content-Type: application/json" \ -d @- <<'EOF'
{ "message": "$1", "chat_history": [], "show_thinking": false, "persona": "default" } EOF
4. **Return JSON**: Returns the full JSON response for Gemini to parse
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.
- 8d ago First seen · 126 lines · 19 tokens per session scan A aff0ac047bd0
ask-sippy is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,350 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to ask-sippy, differing in 32 lines, and is treated as a copy.
Other commands, from other repositories
login
Connect the Supabase CLI to your Supabase account by logging in with your personal access token.
deploy-check
Pre-deployment readiness check for Drupal projects. Validates config, dependencies, security, and deployment scripts.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.