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 get-release-datesgit 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/get-release-dates)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/get-release-dates"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/get-release-dates/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/get-release-dates"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/get-release-dates.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.00015 | $0.01731 |
| Opus 5 | $0.00008 | $0.00865 |
| Sonnet 5 | $0.00003 | $0.00346 |
| Haiku 4.5 | $0.00002 | $0.00173 |
Grade A, and why
Get Release Dates 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get Release Dates
This skill provides functionality to fetch OpenShift release information including GA dates and development start dates from the Sippy API.
When to Use This Skill
Use this skill when you need to:
- Get GA (General Availability) date for a specific OpenShift release
- Find when development started for a release
- Identify the previous release in the sequence
- Validate if a release exists in Sippy
- Determine if a release is in development or has GA'd
Prerequisites
-
Python 3 Installation
- Check if installed:
which python3 - Python 3.6 or later is required
- Comes pre-installed on most systems
- Check if installed:
-
Network Access
- The script requires network access to reach the Sippy API
- Ensure you can make HTTPS requests to
sippy.dptools.openshift.org
Implementation Steps
Step 1: Verify Prerequisites
First, ensure Python 3 is available:
python3 --version
If Python 3 is not installed, guide the user through installation for their platform.
Step 2: Locate the Script
The script is located at:
extensions/teams/skills/get-release-dates/get_release_dates.py
Step 3: Run the Script
Execute the script with the release parameter:
# Get dates for release 4.21
python3 extensions/teams/skills/get-release-dates/get_release_dates.py \
--release 4.21
# Get dates for release 4.20
python3 extensions/teams/skills/get-release-dates/get_release_dates.py \
--release 4.20
Step 4: Process the Output
The script outputs JSON data with the following structure:
{
"release": "4.21",
"found": true,
"ga": "2026-02-17T00:00:00Z",
"development_start": "2025-09-02T00:00:00Z",
"previous_release": "4.20"
}
Field Descriptions:
release: The release identifier that was queriedfound: Boolean indicating if the release exists in Sippyga: GA (General Availability) date. If null, the release is still in development.development_start: When development started for this releaseprevious_release: The previous release in the sequence (empty string if none)
What ships with it
2 files 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.
- 8d ago First seen · 259 lines · 15 tokens per session scan A 0abb6f99fb39
Get Release Dates is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,731 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-09-03.
Other skills, from other repositories
spk-run-verdict-capture
Set a Spec Kitty work-package review verdict through the deterministic event-log seam, so every agent harness records approve/reject the same way.
spk-team-sync
Operate Spec Kitty tracker sync (sync pull/sync push/sync run for local providers) and hosted SaaS-backed mission data.
spk-run-program-orchestrate
Orchestrate multi-repo, multi-mission Spec Kitty programs across dependencies, parallel agents, review gates, merge, and post-merge closeout.
spk-gate-retrospective
Create or verify Spec Kitty mission retrospectives after merge and surface process learnings without blocking completed work.
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
cc-skill-project-guidelines-example
Project Guidelines Skill (Example).