what-iff: Skill for Claude Code

.agents/skills/gh-run-watch/SKILL.md

gh-run-watch is a skill for Claude Code, Codex from theimaginaryfoundation/what-iff. It costs 142 tokens per session (1,757 once invoked), scanned A, original, Apache-2.0.

A helper that waits for a GitHub Actions run, GitHub's automated build and test service, to finish by checking its status periodically. It reports the result without continuously streaming the run's output.

In plain words
What is it for?
Use it after a push, pull request, or manually started workflow when the next step depends on whether CI passed or failed.
Why use it?
It avoids noisy, expensive live output and prevents an agent from waiting forever on a stuck build.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents).

This is theimaginaryfoundation/what-iff's own configuration. It tells Claude Code and Codex how to work on what-iff itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything what-iff configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is npx playwright show-trace ./playwright-report/data/<hash>.zip.

Reuse

Borrowing it

Nothing to install: this file belongs to theimaginaryfoundation/what-iff. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/theimaginaryfoundation/what-iff/main/.agents/skills/gh-run-watch/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/theimaginaryfoundation/what-iff

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for gh-run-watch

README.md
[![agentmods](https://agentmods.dev/badge/skills/theimaginaryfoundation/what-iff/gh-run-watch/github.svg)](https://agentmods.dev/skills/theimaginaryfoundation/what-iff/gh-run-watch)
Your own site
<a href="https://agentmods.dev/skills/theimaginaryfoundation/what-iff/gh-run-watch"><img src="https://agentmods.dev/badge/skills/theimaginaryfoundation/what-iff/gh-run-watch/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.

agentmods 80×15 button for gh-run-watch

Your own site · 80×15
<a href="https://agentmods.dev/skills/theimaginaryfoundation/what-iff/gh-run-watch"><img src="https://agentmods.dev/badge/skills/theimaginaryfoundation/what-iff/gh-run-watch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 142 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,757 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00142 $0.01757
Opus 5 $0.00071 $0.00879
Sonnet 5 $0.00028 $0.00351
Haiku 4.5 $0.00014 $0.00176

Measured yesterday against content hash 0bbd9dc4a21d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

gh-run-watch 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 yesterday.

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.

.agents/skills/gh-run-watch/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Watching a GitHub Actions run cheaply

gh run watch opens a long-lived connection and streams progress. That is expensive in an agent context: the output is large, mostly noise, and it cannot be interrupted cleanly to do something else. This skill polls instead — a handful of small gh api calls, each returning a few bytes.

Rules of thumb

  • Ask for the smallest thing that answers the question. --jq runs server-side output through a filter locally, but the field selection is what keeps the response small; never fetch a whole run object to read one field.
  • Poll on a curve, not a constant. CI jobs take minutes, so a 5-second poll is ~100 wasted requests. Start at 20s, grow to 60s.
  • Only reach for logs after a failure, and only for the job that failed.
  • Never poll without a ceiling. An infinite until loop against a hung run will spin forever.

1. Find the run

Prefer the exact commit — branch lookups race with new pushes and can return a run for a commit you did not make.

SHA=$(git rev-parse HEAD)
REPO=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
RID=$(gh api "repos/$REPO/actions/runs?head_sha=$SHA&per_page=1" --jq '.workflow_runs[0].id')

Narrow to one workflow when several trigger on the same commit:

gh api "repos/$REPO/actions/runs?head_sha=$SHA&per_page=20" \
  --jq '.workflow_runs[] | select(.name == "E2E (mock backend)") | .id' | head -1

A freshly pushed commit may have no run for a few seconds. Poll for the run's existence the same way you poll for its completion, with the same ceiling.

2. Wait for it

One field per request, backing off, bounded:

DEADLINE=$(( $(date +%s) + 1800 ))   # 30 min ceiling — raise for slow suites
SLEEP=20
while :; do
  STATUS=$(gh api "repos/$REPO/actions/runs/$RID" --jq '.status')
  [ "$STATUS" = "completed" ] && break
  [ "$(date +%s)" -ge "$DEADLINE" ] && { echo "timed out waiting for $RID"; break; }
  sleep "$SLEEP"
  [ "$SLEEP" -lt 60 ] && SLEEP=$(( SLEEP + 10 ))
done
gh api "repos/$REPO/actions/runs/$RID" --jq '.conclusion'

Read the full file on GitHub · 160 lines

Changes

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.

  1. yesterday First seen · 160 lines · 142 tokens per session scan A 0bbd9dc4a21d

Subscribe to this mod's changes

gh-run-watch is a skill published in the GitHub repository theimaginaryfoundation/what-iff (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 142 tokens to every session and 1,757 once invoked, about $0.0007 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-09.

Related

Other skills, from other repositories

import-prom-rule

Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…

ccfos/nightingale · 125 tokens

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

atmos-profiles

Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.

cloudposse/atmos · 35 tokens

webhook-management

Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.

hoangsonww/Claude-Code-Agent-Monitor · 56 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens