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.
curl -O https://raw.githubusercontent.com/theimaginaryfoundation/what-iff/main/.agents/skills/gh-run-watch/SKILL.mdgit clone --depth 1 https://github.com/theimaginaryfoundation/what-iffWrote 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/theimaginaryfoundation/what-iff/gh-run-watch)<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.
<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>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.00142 | $0.01757 |
| Opus 5.5 | $0.00057 | $0.00703 |
| Sonnet 5.5 | $0.00028 | $0.00351 |
| Haiku 4.5 | $0.00014 | $0.00176 |
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 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 — 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.
--jqruns 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
untilloop 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'
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 · 160 lines · 142 tokens per session scan A 0bbd9dc4a21d
gh-run-watch is a skill published in the GitHub repository theimaginaryfoundation/what-iff (19 stars, last pushed today), licensed Apache-2.0. It adds 142 tokens to every session and 1,757 once invoked, about $0.0006 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-09.
Other skills, from other repositories
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.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
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.
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.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
ci-fixer
CI failures - read error, minimal fix, verify.