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 ocpbugsgit 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/ocpbugs)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/ocpbugs"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/ocpbugs/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/ocpbugs"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/ocpbugs.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.00021 | $0.02280 |
| Opus 5 | $0.00010 | $0.01140 |
| Sonnet 5 | $0.00004 | $0.00456 |
| Haiku 4.5 | $0.00002 | $0.00228 |
Grade A, and why
OCPBUGS Jira Conventions 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.
OCPBUGS Jira Conventions
This skill provides conventions and requirements for creating bug reports in the OCPBUGS project, which is used by all OpenShift product teams for bug tracking.
When to Use This Skill
Use this skill when creating bugs in the OCPBUGS project:
- Project: OCPBUGS - OpenShift Bugs
- Issue Type: Bug - Bug reports only
This skill is automatically invoked by the /jira:create command when the project_key is "OCPBUGS" or when issue type is "bug" without a project specified.
Project Information
OCPBUGS Project
Full name: OpenShift Bugs
Key: OCPBUGS
Used for: Bugs only
Used by: All OpenShift product teams
Version Requirements
Note: Universal requirements (Security Level: Red Hat Employee, Labels: ai-generated-jira) are defined in the /jira:create command and automatically applied to all tickets.
Affects Version/s (versions)
Purpose: Version where the bug was found
Common values: 4.19, 4.20, 4.21, 4.22, etc.
Handling:
- User should specify the version where they encountered the bug
- If not specified, prompt user: "Which version did you encounter this bug in?"
- Multiple versions can be specified if bug affects multiple releases
Target Version (customfield_10855)
Purpose: Version where the fix is targeted
Common default: openshift-4.21 (or current development release)
Override: May be different based on:
- Severity (critical bugs may target earlier releases)
- Backport requirements
- Release schedule
Never set:
- Fix Version/s (
fixVersions) - This is managed by the release team
Version Override Handling
When user specifies a different version:
- Accept the version as provided
- Validate version exists using MCP tool
jira_get_project_versionsif needed - If version doesn't exist, suggest closest match or ask user to confirm
Component Requirements
IMPORTANT: Component requirements are team-specific.
Some teams require specific components, while others do not. The OCPBUGS skill does NOT enforce component selection.
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 · 21 tokens per session scan A f8a650fe1267
OCPBUGS Jira Conventions is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 2,280 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).