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 fetch-related-triagesgit 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/fetch-related-triages)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/fetch-related-triages"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/fetch-related-triages/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/fetch-related-triages"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/fetch-related-triages.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.00020 | $0.01171 |
| Opus 5 | $0.00010 | $0.00585 |
| Sonnet 5 | $0.00004 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
Fetch Related Triages 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 11d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch Related Triages
Queries the Sippy API to find existing triage records and untriaged regressions that may be related to a given Component Readiness regression. The API matches based on similarly named tests and shared last failure times.
When to Use This Skill
- During regression analysis to find existing triages that could cover the current regression
- To find untriaged regressions that share the same root cause and should be triaged together
- To avoid filing duplicate bugs when a related triage already exists
API Endpoint
GET https://sippy.dptools.openshift.org/api/component_readiness/regressions/{id}/matches
No authentication required (uses production Sippy URL).
Usage
# Fetch all related triages (default: all confidence levels)
python3 extensions/ci/skills/fetch-related-triages/fetch_related_triages.py 35479
# Filter to high confidence matches only
python3 extensions/ci/skills/fetch-related-triages/fetch_related_triages.py 35479 --min-confidence 5
# Human-readable summary
python3 extensions/ci/skills/fetch-related-triages/fetch_related_triages.py 35479 --format summary
Arguments
regression_id(required): The Component Readiness regression ID--min-confidence(optional): Minimum confidence level to include (1-10, default: 1)--format(optional): Output format —json(default) orsummary
Confidence Levels
The API assigns a confidence level (1-10) to each match:
- 10: High confidence — the triage's regressions include the same test (exact test_id match) or very closely related tests with shared failure patterns
- 5: Medium confidence — similarly named tests matched by edit distance, suggesting related tests in the same area
- 2: Low confidence — regressions share the same last failure timestamp, which may indicate they were from the same failing job runs but could be coincidental
Output Format
JSON output
{
"success": true,
"regression_id": 35479,
"triaged_matches": [
{
"triage_id": 370,
"triage_ui_url": "https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/triages/370",
"jira_key": "OCPBUGS-76612",
"jira_url": "https://redhat.atlassian.net/browse/OCPBUGS-76612",
"jira_status": "New",
"jira_summary": "Component Readiness: [Networking / ovn-kubernetes] ...",
"triage_type": "test",
"triage_description": "...",
"confidence_level": 10,
"regressions_on_triage": [
{
"id": 35217,
"test_name": "...",
"test_id": "...",
"component": "Networking / ovn-kubernetes",
"variants": ["..."],
"opened": "...",
"closed": null,
"triages": null,
"last_failure": "..."
}
]
}
],
"untriaged_regressions": [
{
"id": 35480,
"test_name": "...",
"test_id": "...",
"component": "...",
"variants": ["..."],
"opened": "...",
"closed": null,
"triages": null,
"last_failure": "...",
"match_reason": "similarly_named_test",
"edit_distance": 1
}
]
}
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.
- 11d ago First seen · 126 lines · 20 tokens per session scan A 78837367d8f0
Fetch Related Triages is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,171 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
gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
spk-admin-setup-doctor
Install, verify, and repair Spec Kitty commands, skills, agent paths, runtime prerequisites, and common setup failures.
lov-fix-codex-session
A recovery tool for stuck Codex conversations, including broken tool-call records and references to a model provider that no longer exists. Codex is an AI coding assistant, and a provider is the service supplying its model.
lov-obsidian-ensure-dev-sync
A troubleshooting workflow for an Obsidian plugin development chain: building the plugin, copying its files into an Obsidian Vault, and checking hot reload. An Obsidian Vault is the folder where Obsidian stores notes and plugin files.
lov-fix-by-add-log
A debugging assistant that adds a small amount of targeted diagnostic logging and uses the resulting output to investigate a hard-to-reproduce problem.
lov-fix-general
A software troubleshooting workflow for finding the cause of an error, applying a focused fix, and checking the original failing path again.