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 trigger-payload-jobgit 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/trigger-payload-job)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/trigger-payload-job"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/trigger-payload-job/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/trigger-payload-job"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/trigger-payload-job.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.00042 | $0.01685 |
| Opus 5 | $0.00021 | $0.00843 |
| Sonnet 5 | $0.00008 | $0.00337 |
| Haiku 4.5 | $0.00004 | $0.00169 |
Grade A, and why
Trigger Payload Job 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.
curl -sL "<payload_test_url>" | grep -oE 'https://prow\.ci\.openshift\.org/view/gs/test-platform-results/logs/[^"]+' | sort -u This is a copy
98% identical to trigger-payload-job — 4 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger Payload Job
This skill triggers payload validation jobs on a GitHub PR by posting the correct Prow commands as PR comments, then polls for the bot response to collect the resulting job URLs.
When to Use This Skill
This skill MUST be used whenever triggering payload testing on a PR. This includes revert PRs, draft experimental revert PRs, or any PR that needs payload validation. Do not post payload commands without following this skill — the command syntax is specific and other formats will be silently ignored by the bot.
Inputs (passed in-context by the caller):
pr_url: The GitHub PR URL to trigger jobs on (e.g.,https://github.com/openshift/ovn-kubernetes/pull/3040)org,repo,pr_number: Parsed from the PR URLjobs: List of jobs to trigger, each with:job_name: The full job name (e.g.,aggregated-hypershift-ovn-conformance-4.22)is_aggregated: Whether this is an aggregated job (hasaggregated-prefix)underlying_job_name: For aggregated jobs only — the underlying periodic job name (e.g.,periodic-ci-openshift-hypershift-release-4.22-periodics-e2e-aws-ovn-conformance). This MUST be extracted from the aggregated job's junit artifacts by the caller's analysis — it cannot be derived from the aggregated job name.count: For aggregated jobs only — how many runs (default: 10). Use judgement: fewer runs when triggering many jobs to limit resource consumption, more when only one or two jobs need validation.
Prerequisites
- GitHub CLI (
gh): Installed and authenticated - Repository Access: User must have permission to comment on the PR
Job Triggering Limits
The caller is responsible for enforcing global limits before invoking this skill. However, this skill also enforces the following hard limits per invocation:
- Non-aggregated jobs: No more than 5 per comment
- Aggregated jobs: No more than 1 per comment. Aggregated jobs are expensive (they run many iterations), so only trigger one at a time. A second aggregated job should only be triggered after the first completes, and only if confirmation is needed.
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 · 135 lines · 42 tokens per session scan A c5ed4db98aaa
Trigger Payload Job is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,685 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 98% identical to trigger-payload-job, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
skillgrade-setup
Sets up and runs skillgrade evaluation pipelines for Agent Skills. Use when initializing eval configurations, running trials, reviewing results, or integrating with CI. Don't use for writing grader scripts, general test authoring, or non-agentic documentation.
onboard-repo
Index an unfamiliar codebase into the knowledge graph, then produce a first orientation map -- entry points, most-depended-upon modules, hotspots, test topology.
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
lov-fix-until-no-error
A verification-focused debugging workflow that repeatedly runs specified checks, fixes the highest-priority failure, and stops when the checks pass or a genuine external blockage remains.
exploit-xss
Cross-site scripting (XSS) vulnerability detection and exploitation. Supports reflected XSS, stored XSS, DOM-based XSS, and blind XSS testing. Use this skill when user mentions XSS, cross-site scripting, script injection, or needs to test JavaScript injection in parameters, forms, headers, or DOM sources.
platform-pre-review
Platform Developer: Stage 4a pre-review task. Run lint, type-check, SCA, license check, security trigger, and hygiene checks. Produce pipeline/gates/stage-04a.json.