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 agentmods add skills/nvidia/openshell/watch-github-actionsnpx skills add NVIDIA/OpenShell --skill watch-github-actionsgit clone --depth 1 https://github.com/NVIDIA/OpenShellWhat 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 | $0.00073 | $0.01271 |
| Opus 5 | $0.00036 | $0.00635 |
| Sonnet 5 | $0.00015 | $0.00254 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
watch-github-actions 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 2d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watch GitHub Actions
Monitor GitHub Actions workflow runs using the gh CLI.
Prerequisites
- The
ghCLI must be authenticated (gh auth status) - You must be in a git repository with a GitHub remote
Quick Status Check
List recent workflow runs for the current branch:
gh run list --branch "$(git branch --show-current)"
List all recent runs:
gh run list
Watch a Run in Real Time
Watch a workflow run until it completes:
gh run watch
Watch a specific run:
gh run watch <run-id>
This will continuously update the status until the run finishes (success, failure, or cancelled).
View Run Details
View a specific run with job details:
gh run view <run-id>
View with full log output:
gh run view <run-id> --log
View a failed job's log:
gh run view <run-id> --log-failed
Check Runs for a Specific Branch
Current branch:
gh run list --branch "$(git branch --show-current)"
Specific branch:
gh run list --branch main
gh run list --branch feature-branch
Check Runs for a PR
List workflow runs associated with a PR:
# Get the head branch of the PR, then list runs
BRANCH=$(gh pr view <pr-number> --json headRefName --jq '.headRefName')
gh run list --branch "$BRANCH"
Or view the checks directly on the PR:
gh pr checks <pr-number>
List Recent Runs
List runs for the current project:
gh run list
Filter by status:
gh run list --status failure
gh run list --status success
gh run list --status in_progress
Filter by workflow:
gh run list --workflow "CI"
JSON output for scripting:
gh run list --json databaseId,status,headBranch,url --jq '.[] | {id: .databaseId, status: .status, branch: .headBranch, url: .url}'
View Job Logs
View logs for a specific run:
gh run view <run-id> --log
View only failed job logs:
gh run view <run-id> --log-failed
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.
- 2d ago First seen · 221 lines · 73 tokens per session scan A b583d4dac0e8
watch-github-actions is a skill published in the GitHub repository NVIDIA/OpenShell (8,421 stars, last pushed 2d ago), licensed Apache-2.0. It adds 73 tokens to every session and 1,271 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…