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.
git clone --depth 1 https://github.com/spideynolove/claude-dotfilesWrote 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/commands/spideynolove/claude-dotfiles/check-github-ci)<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/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/commands/spideynolove/claude-dotfiles/check-github-ci"><img src="https://agentmods.dev/badge/commands/spideynolove/claude-dotfiles/check-github-ci.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.00011 | $0.00437 |
| Opus 5.5 | $0.00004 | $0.00175 |
| Sonnet 5.5 | $0.00002 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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 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.
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 checksas needed
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 · 59 lines · 11 tokens per session scan A 48525550a2c5
check-github-ci is a command published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 437 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
security-check
Fast security baseline audit of a product — tracked secrets, unpinned/vulnerable GitHub Actions, workflow permission scope, untrusted-input triggers, MCP-config surface, and an RLS reminder. Add --live to also check the RUNNING system for drift (live RLS status, storage-bucket visibility, Security Advisors, preview…