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 commands/kaeawc/auto-mobile/check-cigit clone --depth 1 https://github.com/kaeawc/auto-mobileWrote 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/kaeawc/auto-mobile/check-ci)<a href="https://agentmods.dev/commands/kaeawc/auto-mobile/check-ci"><img src="https://agentmods.dev/badge/commands/kaeawc/auto-mobile/check-ci.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.01257 |
| Opus 5 | $0.00019 | $0.00629 |
| Sonnet 5 | $0.00008 | $0.00251 |
| Haiku 4.5 | $0.00004 | $0.00126 |
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 5d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage a PR's CI: head-scoped check state, failing-job logs (live or complete), causal classification, local reproduction, and the safe next step. Takes a PR number, or resolves one from the current branch.
scripts/ci/pr-failing-job-logs.sh "$ARGUMENTS"
What the script does
The script branches on bucket (gh's normalized state) rather than grepping human-readable
output, then walks run → jobs → each failed job's log. A finished job's log is readable while
sibling jobs still run, so it never waits on the slowest leg; when a job hasn't finished its log
404s and the script falls back to per-step status. Logs land in scratch/ at ~100KB each — read
the extracted error lines first.
Triage workflow
- 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. - Collect
gh pr checks <pr> --json name,state,bucket,link,workflowplus paginatedrepos/<owner>/<repo>/commits/<head-sha>/check-runs. Branch onbucket: onlyfailis a failure —skippingandcancelare 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. - 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.
- For a completed failed job:
gh run view <run-id> --job <job-id> --log-failed, orgh 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 --followdoes not exist; use--paginate. - If the log is truncated or lacks the failure body, list the run's artifacts and read the
relevant one. If
gh run downloadis unauthorized, state that exact blocker — do not infer a root cause from partial evidence. - 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. - Reproduce a PR-caused failure locally with the narrowest authoritative command.
- After any push, restart at step 1 — every check, thread, and comment was scoped to the previous SHA.
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.
- 5d ago First seen · 99 lines · 38 tokens per session scan A c18030485d28
check-ci is a command published in the GitHub repository kaeawc/auto-mobile (46 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 1,257 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.
Other commands, from other repositories
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
actions
Command "actions" from openclaw/crabbox, covering actions, subcommands, hydrate, register and dispatch.
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.