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 skills add tomzx/agents --skill handle-pr-cigit clone --depth 1 https://github.com/tomzx/agentsWrote 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/skills/tomzx/agents/handle-pr-ci)<a href="https://agentmods.dev/skills/tomzx/agents/handle-pr-ci"><img src="https://agentmods.dev/badge/skills/tomzx/agents/handle-pr-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.1 | $0.00028 | $0.00862 |
| Opus 5 | $0.00014 | $0.00431 |
| Sonnet 5 | $0.00006 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
handle-pr-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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handle PR CI
Fetches failing CI check logs for a pull request, diagnoses the root cause of each failure, implements fixes, pushes, and confirms all checks pass.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, target the pull request from
$PR_NUMBER(and$REPO). ghCLI authenticated with read/write access to the target repository- PR number (
$1) identifying an open pull request with at least one failing CI check
Workflow
Fetch CI check status ($1)
|
v
Any failing checks?
/ \
Yes No
| |
v v
Fetch logs Report all
per failure checks green, stop
|
v
Diagnose root cause
|
v
Implement fix
|
v
Present fix to user for approval
/ \
Approved Rejected
| |
v v
Commit + push Stop
|
v
Monitor CI re-run
|
v
All checks green?
/ \
Yes No
| |
v v
Done Loop back to
fetch logs
Steps
-
Fetch the current CI check status:
gh pr checks $1 --watch=false -
If all checks are passing, report success and stop.
-
For each failing check, fetch its log output:
gh run view <run-id> --log-failed -
Diagnose the root cause of each failure. Distinguish between:
- Flaky/transient failures (network timeouts, rate limits): note as transient, suggest re-running rather than a code fix.
- Code failures (test failures, lint errors, type errors, build errors): identify the specific file and line causing the failure.
-
For code failures, implement the fix in the codebase.
-
Present the diagnosis and proposed fix to the user for approval before committing.
-
On approval, commit and push:
git add <changed files> git commit -m "<fix description>" git push -
Monitor the CI re-run until checks complete:
gh pr checks $1 --watch
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.
- 4d ago First seen · 126 lines · 28 tokens per session scan A 65d256a4ed44
handle-pr-ci is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 862 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-09-03.
Other skills, from other repositories
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…
github-ci-fix
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
github-ci-fix
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.