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-regression)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/analyze-regression"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-regression/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/analyze-regression"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/analyze-regression.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.00012 | $0.16801 |
| Opus 5 | $0.00006 | $0.08400 |
| Sonnet 5 | $0.00002 | $0.03360 |
| Haiku 4.5 | $0.00001 | $0.01680 |
Grade A, and why
analyze-regression 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 9d 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 — 1,245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
ci:analyze-regression
Synopsis
/ci:analyze-regression <regression id>
Description
The ci:analyze-regression command analyzes details for a specific Component Readiness regression and suggests next steps for investigation.
The command performs a full analysis regardless of whether the regression has been triaged. For triaged regressions, it also fetches the linked JIRA issue to analyze whether someone is actively working on the fix or if the issue needs attention.
This command is useful for:
- Understanding regression patterns and failure modes
- Checking if a triaged regression is being actively worked on or needs attention
- Identifying related regressions that might be caused by the same issue
- Getting pointers on where to investigate next
Implementation
Important: Avoiding user permission prompts when running scripts
When calling Python skill scripts via the Bash tool, always run the script directly without piping the output through inline Python (python3 -c "..."). Complex piped commands trigger user permission prompts, while simple python3 script.py args calls are auto-approved.
- Do:
python3 script.py args --format json 2>/dev/null— run the script directly and process the JSON output in your reasoning - Don't:
python3 script.py args | python3 -c "import json; ..."— piped inline Python triggers permission prompts
Parse and analyze the JSON output from scripts using your own reasoning capabilities rather than shell pipelines.
-
Load CI Context: Read all documentation files in
extensions/ci/docs/for context on tests, jobs, and CI conventions. These contain important notes on specific test frameworks, job ownership, and debugging guidance that should inform the analysis.ls extensions/ci/docs/Read each file found. Keep this context in mind throughout the analysis — it may affect how you interpret failure patterns, who to recommend contacting, or what the root cause is likely to be.
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.
- 9d ago First seen · 1,245 lines · 12 tokens per session scan A 784815da448c
analyze-regression is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 16,801 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
audit
Run a structured codebase audit. Maps the architecture, assesses health (compliance, tests, docs), performs deep analysis (security, performance, code quality), and synthesizes a prioritized roadmap. Outputs land under docs/audit/ in this project. Phases 0-3 with human checkpoints between each phase. Use /audit-quick…
wtfp:report-bug
Collect a reproducible bug report and publish it only after explicit user approval.
fix
Diagnose and fix bugs, errors, and issues in code.
bug-report
Structured bug-fix protocol per docs/methodology/bug-protocol.md. Use when asked to '/bug-report', 'I found a bug', 'something is broken', 'fix this bug', 'report a bug', 'this is broken'.
bmad-review-adversarial-general
Deprecated — forwards to bmad-review.
bmad-review-edge-case-hunter
Deprecated — forwards to bmad-review.