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 openshift-eng/ai-helpers --skill fetch-tide-pr-statusgit clone --depth 1 https://github.com/openshift-eng/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/openshift-eng/ai-helpers/fetch-tide-pr-status)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/fetch-tide-pr-status"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/fetch-tide-pr-status/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/openshift-eng/ai-helpers/fetch-tide-pr-status"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/fetch-tide-pr-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00707 |
| Opus 5.5 | $0.00014 | $0.00283 |
| Sonnet 5.5 | $0.00007 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
fetch-tide-pr-status 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 1mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch Tide PR Status
CLI equivalent of the Prow PR Status page. Focuses on labels and required jobs — the most common merge blockers. Tide also checks other things (author, milestone) which may appear in the tide verdict but are not broken out here.
Only outputs open, non-draft PRs.
Prerequisites
ghCLI authenticatedpython3withpyyaml(pip install pyyaml)
Usage
# All open PRs by an author
python3 "${SKILL_DIR}/fetch_tide_pr_status.py" openshift/cluster-monitoring-operator machine424
# Specific PRs
python3 "${SKILL_DIR}/fetch_tide_pr_status.py" openshift/cluster-monitoring-operator 3057,3044
Output
JSON array, one object per PR:
[
{
"number": 3044,
"title": "OCPBUGS-105305: [release-4.21] wrap ...",
"author": "machine424",
"url": "https://github.com/openshift/cluster-monitoring-operator/pull/3044",
"branch": "release-4.21",
"state": "open",
"mergeable": true,
"tide": "Not mergeable. Needs jira/valid-bug label.",
"blockers": [
"missing required label: jira/valid-bug",
"has forbidden label: jira/invalid-bug",
"job not passing: ci/prow/e2e-aws-ovn (running)"
],
"labels": {
"met": false,
"required": {
"have": ["lgtm", "approved"],
"missing": ["jira/valid-bug"]
},
"forbidden": {
"have": ["jira/invalid-bug"],
"clear": ["needs-rebase", "do-not-merge/hold"]
}
},
"required_jobs": [
{"name": "ci/prow/unit", "state": "success"},
{"name": "ci/prow/e2e-aws-ovn", "state": "running", "description": "Job triggered."}
]
}
]
tide — Tide's own verdict. blockers — what's preventing merge. required_jobs — non-optional jobs from openshift/release config; if the config could not be fetched, contains a single {"error": "..."} entry instead of jobs (not reflected in blockers).
Data Sources
https://prow.ci.openshift.org/tide.js— required/forbidden labels (public)gh api repos/{o}/{r}/pulls/{n}— PR metadatagh api repos/{o}/{r}/commits/{sha}/status— job statuses + Tide contextraw.githubusercontent.com/openshift/release/master/ci-operator/jobs/...— presubmit config (required vs optional)
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.
- 1mo ago First seen · 75 lines · 36 tokens per session scan A 53a9821b2642
fetch-tide-pr-status is a skill published in the GitHub repository openshift-eng/ai-helpers (119 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 707 once invoked, about $0.0001 per session on Opus 5.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
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.
resolve-handoff
Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.