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/analyze-payload)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/analyze-payload"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-payload.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.00025 | $0.01315 |
| Opus 5 | $0.00013 | $0.00658 |
| Sonnet 5 | $0.00005 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
analyze-payload 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 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.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:analyze-payload
Synopsis
/ci:analyze-payload <payload-tag> [--lookback N]
Description
The ci:analyze-payload command analyzes a specific payload tag, investigates every failed blocking job, and produces a self-contained HTML report summarizing what went wrong.
It supports Rejected payloads (full analysis), Ready payloads (early analysis of blocking jobs that have already failed, to determine if the payload is on track for rejection), and Accepted payloads (which may have been force-accepted despite blocking job failures).
It performs historical lookback through consecutive rejected payloads to determine when each failure first appeared. For each originating payload (where a job first started failing), it fetches the new PRs introduced in that payload as likely culprits. This distinguishes new failures from persistent/permafailing jobs and helps identify the root cause commits.
When a candidate PR can be correlated with high confidence (>= 85 rubric score) to a blocking job failure — based on component match, error analysis, and timing — the report will recommend it for immediate revert. Per OCP policy, PRs that break payloads MUST be reverted; fixes can be re-landed after the revert restores payload health. The /ci:payload-revert command can then be used to automatically create TRT JIRA bugs, open revert PRs, and trigger payload validation jobs for all high-confidence candidates.
The payload results YAML output (payload-results-{tag}.yaml) can be consumed by composable downstream commands: /ci:payload-revert stages reverts for high-confidence candidates, and /ci:payload-experiment opens draft revert PRs for medium-confidence candidates to experimentally determine causality.
Failed jobs are investigated in parallel using subagents with the appropriate analysis skill (install failure vs test failure).
Key Features
- Historical lookback: Walks back through up to N consecutive rejected payloads (default 10) to find when each job first started failing
- PR correlation: Uses the
fetch-new-prs-in-payloadskill to identify PRs that landed in the originating payload for each failure - Parallel investigation: Kicks off subagents for each failed blocking job using the appropriate CI analysis skill
- Revert recommendations: Proposes specific PRs to revert when the evidence strongly links them to a failure
- HTML report: Generates an attractive, self-contained HTML report with collapsible sections, color-coded severity, and executive summary
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 · 96 lines · 25 tokens per session scan A cb814466a273
analyze-payload is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,315 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 commands, from other repositories
wtfp:update
Check for a newer compatible package or plugin release and install it only after approval.
reqforge-greenkeeper
Diagnose and fix ReqForge repository release gate failures.
create-release-note.zh-CN
A command that creates release notes from pull requests and commits. Release notes summarize changes included in a software version.
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.