check-github-ci

check-github-ci is a command for Claude Code from spideynolove/claude-dotfiles. It costs 11 tokens per session (437 once invoked), scanned A, original, MIT.

A command for checking GitHub Actions, GitHub’s service for automatically building and testing code, and following each run until it finishes.

In plain words
What is it for?
Use it after opening or updating a pull request to inspect CI results, review failed checks, guide fixes, and confirm the checks pass afterward.
Why use it?
It avoids repeatedly checking a pull request by hand and makes it easier to see whether builds, tests, linting, or security checks failed.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/spideynolove/claude-dotfiles/check-github-ci
Clone the repo
git clone --depth 1 https://github.com/spideynolove/claude-dotfiles

Made for: Claude Code.

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 check-github-ci

README.md
[![agentmods](https://agentmods.dev/badge/commands/spideynolove/claude-dotfiles/check-github-ci.svg)](https://agentmods.dev/commands/spideynolove/claude-dotfiles/check-github-ci)
Your own site
<a href="https://agentmods.dev/commands/spideynolove/claude-dotfiles/check-github-ci"><img src="https://agentmods.dev/badge/commands/spideynolove/claude-dotfiles/check-github-ci.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 437 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00011 $0.00437
Opus 5 $0.00005 $0.00218
Sonnet 5 $0.00002 $0.00087
Haiku 4.5 $0.00001 $0.00044

Measured 4d ago against content hash 48525550a2c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check-github-ci 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 4d 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.

.claude-global-backup/commands/check-github-ci.md · 59 lines

What it actually says

GitHub CI Monitoring

Monitors GitHub Actions CI status and tracks until completion.

Usage

# Check CI status
gh pr checks

Basic Examples

# Check CI after creating PR
gh pr create --title "Add new feature" --body "Description"
gh pr checks

Collaboration with Claude

# Flow from CI check to correction
gh pr checks
"Analyze CI check results and suggest fixes if there are failures"

# Recheck after correction
git push origin feature-branch
gh pr checks
"Check CI results after correction to confirm no issues"

Example Execution Results

All checks were successful
0 cancelled, 0 failing, 8 successful, 3 skipped, and 0 pending checks

   NAME                                    DESCRIPTION                ELAPSED  URL
○  Build/test (pull_request)                                          5m20s    https://github.com/user/repo/actions/runs/123456789
○  Build/lint (pull_request)                                          2m15s    https://github.com/user/repo/actions/runs/123456789
○  Security/scan (pull_request)                                       1m30s    https://github.com/user/repo/actions/runs/123456789
○  Type Check (pull_request)                                          45s      https://github.com/user/repo/actions/runs/123456789
○  Commit Messages (pull_request)                                     12s      https://github.com/user/repo/actions/runs/123456789
-  Deploy Preview (pull_request)                                               https://github.com/user/repo/actions/runs/123456789
-  Visual Test (pull_request)                                                  https://github.com/user/repo/actions/runs/123456789

Notes

  • Check details when failed
  • Wait for all checks to complete before merging
  • Re-run gh pr checks as needed
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. 4d ago First seen · 59 lines · 11 tokens per session scan A 48525550a2c5

Subscribe to this mod's changes

check-github-ci is a command published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 437 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-08-31.