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 skills add wangke19/gemini-ai-helpers --skill prow-job-artifact-searchgit 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/skills/wangke19/gemini-ai-helpers/prow-job-artifact-search)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/prow-job-artifact-search"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/prow-job-artifact-search/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/skills/wangke19/gemini-ai-helpers/prow-job-artifact-search"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/prow-job-artifact-search.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.00028 | $0.02292 |
| Opus 5 | $0.00014 | $0.01146 |
| Sonnet 5 | $0.00006 | $0.00458 |
| Haiku 4.5 | $0.00003 | $0.00229 |
Grade A, and why
Prow Job Artifact Search 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 12d 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.
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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prow Job Artifact Search
This skill provides a reusable Python script for browsing, searching, and fetching artifacts from Prow CI job runs stored in the test-platform-results GCS bucket. It wraps gcloud storage commands so callers do not need to construct GCS URIs or manage the CLI directly.
When to Use This Skill
Use this skill when you need to:
- Browse the artifact directory tree of a Prow job run
- Search for specific files within a job's artifacts (e.g., interval files, node logs, journal logs)
- Fetch the contents of a specific artifact file for analysis
- Discover what artifacts are available before running a more targeted analysis skill
This skill is a building block used by other analysis workflows. Use it when you need ad-hoc artifact access that is not covered by a dedicated analysis skill.
Prerequisites
-
gcloud CLI Installation
- Check if installed:
which gcloud - If not installed, provide instructions for the user's platform
- Installation guide: https://cloud.google.com/sdk/docs/install
- Check if installed:
-
gcloud Authentication (Optional)
- The
test-platform-resultsbucket is publicly accessible - No authentication is required for read access
- The
-
Python 3 (3.6 or later)
- Check:
which python3
- Check:
Script Location
extensions/ci/skills/prow-job-artifact-search/prow_job_artifact_search.py
Operations
list — List directory contents
List files and subdirectories at a given path within the job's artifact tree.
python3 extensions/ci/skills/prow-job-artifact-search/prow_job_artifact_search.py \
<prow-url> list [subpath]
Arguments:
prow-url(required): The Prow job URLsubpath(optional): Subdirectory path relative to the job root. If omitted, lists the job root.
Examples:
# List the job root
python3 .../prow_job_artifact_search.py "https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-.../1234567890" list
# List e2e test artifacts
python3 .../prow_job_artifact_search.py <url> list artifacts/e2e-test/openshift-e2e-test
# List gather-extra oc_cmds
python3 .../prow_job_artifact_search.py <url> list artifacts/e2e-test/gather-extra/artifacts/oc_cmds
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 260 lines · 28 tokens per session scan A 5e8e65574bfe
Prow Job Artifact Search is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 2,292 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
lov-npm-publisher
An npm package publishing workflow that sets up releases through GitHub Actions using OIDC, a login-free trust method, or a local granular NPM token. It covers initial setup, publishing, audit checks, and verifying the package on the npm registry.
glab-cli
GitLab CLI (glab) reference and workflow for repository, merge request, issue, CI/CD, release, and API operations across GitLab.com and self-managed or dedicated instances. Use when Codex needs to run or explain glab commands, usually by relying on the current glab context first, and only falling back to git remote -v…
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
install-gemini-code-review-action
Installs, configures, or upgrades Dazbo's PR code review & issue triage GitHub Action (gemini-review-action) in a target repository. Use when the user wants to set up, configure, or update automated AI code reviews, issue triaging, or Gemini model workflows for their GitHub repository.
github-actions
Configure GitHub Actions for Python CI, PyPI Trusted Publishing, and signed Dockerfile images, with mise, actionlint, and zizmor. Use when adding or fixing Python workflows.
new-project
Bootstrap a new repository by composing the stack, license, mise, lefthook, dprint, CI, agent files, GitHub settings, and first release skills. Use when creating a project.