check-ci

check-ci is a skill for Claude Code from kaeawc/auto-mobile. It costs 49 tokens per session (780 once invoked), scanned A, original, Apache-2.0.

A workflow for investigating failed or waiting checks on a GitHub pull request, which is a proposed change to a code repository.

In plain words
What is it for?
It helps inspect checks, workflow runs, jobs, logs, and artifacts; reproduce likely failures locally; and report the safest next step.
Why use it?
It distinguishes current failures from old or skipped runs and uses the exact pull-request version when examining logs and causes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the auto-mobile plugin — 17 skills, 9 commands, 1 hook, 1 MCP server shipped together

Good fit It helps inspect checks, workflow runs, jobs, logs, and artifacts; reproduce likely failures locally; and report the safest next step.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kaeawc/auto-mobile/check-ci
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.

Any agent
npx skills add kaeawc/auto-mobile --skill check-ci
Clone the repo
git clone --depth 1 https://github.com/kaeawc/auto-mobile

Made for: Claude Code.

Or install auto-mobile, the plugin that ships this one along with the rest of its 17 skills, 9 commands, 1 hook, 1 MCP server.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/kaeawc/auto-mobile/check-ci.svg)](https://agentmods.dev/skills/kaeawc/auto-mobile/check-ci)
Your own site
<a href="https://agentmods.dev/skills/kaeawc/auto-mobile/check-ci"><img src="https://agentmods.dev/badge/skills/kaeawc/auto-mobile/check-ci.svg" alt="Measured on agentmods" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 780 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00049 $0.00780
Opus 5 $0.00024 $0.00390
Sonnet 5 $0.00010 $0.00156
Haiku 4.5 $0.00005 $0.00078

Measured 8d ago against content hash 0fe88802db26, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

check-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 8d 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.

skills/check-ci/SKILL.md · 60 lines

How it starts

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

Check CI

Use this for PR health checks and failure triage.

  • This is narrower than pr-analysis: prefer check-ci when the main question is why checks are failing or blocked.
  • This is read-only unless the user also asks to fix the problem.

Workflow

  1. Resolve the PR number and snapshot headRefOid, baseRefOid, mergeability, and merge state. Use that SHA for every subsequent query. An empty legacy combined status is inconclusive, not green.
  2. Collect gh pr checks <pr> --json name,state,bucket,link,workflow plus paginated repos/<owner>/<repo>/commits/<head-sha>/check-runs. Branch on bucket: only fail is a failure — skipping and cancel are not. Flag duplicate check names with different conclusions on the same head (a cancelled older run beside a successful newer one); the stale one is what parks automerge.
  3. Enumerate runs for that head SHA, then each run's jobs. Ignore runs for older SHAs. Queued and in-progress jobs stay pending — they are never implicitly green.
  4. For a completed failed job: gh run view <run-id> --job <job-id> --log-failed, or gh api repos/<owner>/<repo>/actions/jobs/<job-id>/logs — the latter works as soon as that job finishes, even while sibling jobs still run, so it does not wait on the slowest leg. For a job still executing, gh api .../actions/jobs/<job-id> returns per-step status naming the running or failed step. gh api --follow does not exist; use --paginate.
  5. If the log is truncated or lacks the failure body, list the run's artifacts and read the relevant one. If gh run download is unauthorized, state that exact blocker — do not infer a root cause from partial evidence.
  6. Classify every red result as PR-caused, pre-existing on main, transient/infrastructure, or unproven, grounded in the job log, the changed paths, and current origin/main. Re-run a job only when the evidence supports transience. Never change code for an unrelated or unproven failure.
  7. Reproduce a PR-caused failure locally with the narrowest authoritative command.
  8. After any push, restart at step 1 — every check, thread, and comment was scoped to the previous SHA.

Read the full file on GitHub · 60 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. 8d ago First seen · 60 lines · 49 tokens per session scan A 0fe88802db26

Subscribe to this mod's changes

check-ci is a skill published in the GitHub repository kaeawc/auto-mobile (46 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 780 once invoked, about $0.0002 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.

Related

Other skills, from other repositories