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/query-job-status)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/query-job-status"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/query-job-status/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/query-job-status"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/query-job-status.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.00011 | $0.01134 |
| Opus 5 | $0.00005 | $0.00567 |
| Sonnet 5 | $0.00002 | $0.00227 |
| Haiku 4.5 | $0.00001 | $0.00113 |
Grade A, and why
query-job-status 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 10d 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.
2. **Execute API Request**: Make a GET request to query the job status using the `oc-auth` skill's curl wrapper: How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:query-job-status
Synopsis
/query-job-status <execution-id>
Description
The query-job-status command queries the status of a gangway job execution via the REST API using the execution ID returned when a job is triggered.
The command accepts:
- Execution ID (required, UUID returned when triggering a job)
It makes a GET request to the gangway API and returns the current status of the job including its name, type, status, and GCS path to artifacts if available. The curl_with_token.sh wrapper handles all authentication automatically.
Implementation
The command performs the following steps:
-
Parse Arguments:
- $1: execution ID (required, UUID format)
-
Execute API Request: Make a GET request to query the job status using the
oc-authskill's curl wrapper:# Use curl_with_token.sh from oc-auth skill - it automatically adds the OAuth token # app.ci cluster API: https://api.ci.l2s4.p1.openshiftapps.com:6443 curl_with_token.sh https://api.ci.l2s4.p1.openshiftapps.com:6443 -X GET \ https://gangway-ci.apps.ci.l2s4.p1.openshiftapps.com/v1/executions/<EXECUTION_ID>The
curl_with_token.shwrapper retrieves the OAuth token from the app.ci cluster and adds it as an Authorization header automatically, without exposing the token. -
Display Results: Parse and present the JSON response with:
id: The execution IDjob_name: The name of the jobjob_type: The type of job execution (PERIODIC, POSTSUBMIT, PRESUBMIT)job_status: Current status (SUCCESS, FAILURE, PENDING, RUNNING, ABORTED)gcs_path: Path to job artifacts in GCS (if available)
-
Offer Follow-up Actions:
- If status is PENDING or RUNNING: Offer to check again after a delay
- If status is SUCCESS or FAILURE with gcs_path: Offer to help access logs/artifacts
Return Value
- Success: JSON response with job status details
- Error: HTTP error, authentication failure, or invalid execution ID
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.
- 10d ago First seen · 103 lines · 11 tokens per session scan A 1b600dc0bac2
query-job-status is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,134 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.