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 bradlay/claude-code-recipes --skill pr-ci-watchgit clone --depth 1 https://github.com/bradlay/claude-code-recipesWrote 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/bradlay/claude-code-recipes/pr-ci-watch)<a href="https://agentmods.dev/skills/bradlay/claude-code-recipes/pr-ci-watch"><img src="https://agentmods.dev/badge/skills/bradlay/claude-code-recipes/pr-ci-watch/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/skills/bradlay/claude-code-recipes/pr-ci-watch"><img src="https://agentmods.dev/badge/skills/bradlay/claude-code-recipes/pr-ci-watch.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.00061 | $0.00402 |
| Opus 5.5 | $0.00024 | $0.00161 |
| Sonnet 5.5 | $0.00012 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
pr-ci-watch 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 18d 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
PR CI Watch (report only)
Check CI status on the current repository's open pull requests. Report which are ready to merge and which have failing checks. This skill never merges; a human does.
Requires the GitHub CLI (gh), authenticated for the repository.
Steps
- List open PRs, optionally filtered to a base branch:
gh pr list --state open --json number,title,headRefName,baseRefName,isDraft(add--base <base-branch>when the user names one). - For each PR:
gh pr checks <number>and, if needed,gh pr view <number> --json mergeable,reviewDecision. - Report one line per PR:
- number, title, head and base branch
- checks: passing, failing (name the failing check), or pending (n of m done)
- if every check passes and it is mergeable: suggest
gh pr merge <number>with the repository's usual merge method
- Keep it to one line per PR plus a one-line summary.
Example output
my-repo open PRs:
#174 feature-x -> main: checks passing, ready to merge (gh pr merge 174)
#175 deps-bump -> main: checks pending (2/3 complete)
#176 fix-y -> main: failing: unit-tests
With /loop
/loop 5m /pr-ci-watch
Stop the loop once nothing is pending.
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.
- 18d ago First seen · 45 lines · 61 tokens per session scan A e04d91325405
pr-ci-watch is a skill published in the GitHub repository bradlay/claude-code-recipes (2 stars, last pushed 4d ago), licensed MIT. It adds 61 tokens to every session and 402 once invoked, about $0.0002 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-10-17.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
emerging-techniques-model-merging
Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
release-safety
Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.