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 thettwe/nyann --skill wait-for-pr-checksgit clone --depth 1 https://github.com/thettwe/nyannWrote 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/thettwe/nyann/wait-for-pr-checks)<a href="https://agentmods.dev/skills/thettwe/nyann/wait-for-pr-checks"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/wait-for-pr-checks/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/thettwe/nyann/wait-for-pr-checks"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/wait-for-pr-checks.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.00148 | $0.00772 |
| Opus 5.5 | $0.00059 | $0.00309 |
| Sonnet 5.5 | $0.00030 | $0.00154 |
| Haiku 4.5 | $0.00015 | $0.00077 |
Grade A, and why
wait-for-pr-checks 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wait-for-pr-checks
Wraps bin/wait-for-pr-checks.sh. Poll-based; uses gh pr checks <num> under the hood. The script is the same one release.sh will
uses to gate the tag step (when --wait-for-checks is passed),
so the contract is shared.
1. Resolve the PR number
The script auto-resolves from the current branch via gh pr view,
so the most common invocation is:
bin/wait-for-pr-checks.sh --target <cwd>
Pass --pr <number> when watching a PR you don't have checked out.
2. Tune timeout and cadence
Defaults:
--timeout 1800(30 minutes)--interval 30(poll every 30 seconds)
Bump timeout for slow CI matrices ("integration tests take 90 min"
→ --timeout 7200). Drop interval for snappy local CI ("we Just
hit go" → --interval 10). Don't go below 10 seconds — gh API
rate limits start to bite.
3. Interpret the outcome
The script emits a PRChecksResult JSON. Branch on .outcome:
| Outcome | Meaning | What the user should do |
|---|---|---|
pass |
every check completed with a passing conclusion | proceed with the gated action (merge, tag, deploy) |
no-checks |
PR has no checks attached | proceed; treat as pass |
fail |
at least one check failed (loop bailed early) | open the linked workflow; don't proceed |
timeout |
deadline reached, some still in_progress | retry with a longer timeout, or investigate slow runners |
skipped |
gh missing/unauthenticated, or PR couldn't be resolved | tell the user; can't proceed |
Exit code mirrors the outcome: 0 for pass / no-checks / skipped, 3
for fail / timeout — caller scripts can gate on $?.
4. Combining with merge
This skill only waits. To wait-then-merge in one step, use
/nyann:ship — it opens a PR and merges it in one flow (either via
GitHub auto-merge or by polling CI client-side). Reserve this skill
for cases where the user wants the wait surfaced explicitly (release
runs, manual gating).
When to hand off
- "Merge it for me when CI passes" →
/nyann:ship(opens a PR and merges it, waiting for CI as needed). - "I just want the current status, don't wait" →
gh pr checksdirectly; no polling needed. - "Why did check X fail?" →
gh run view <run-id> --log-failed; this skill only reports outcomes, not log contents.
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 · 75 lines · 148 tokens per session scan A 09c00ed888a9
wait-for-pr-checks is a skill published in the GitHub repository thettwe/nyann (7 stars, last pushed 4d ago), licensed MIT. It adds 148 tokens to every session and 772 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
pr-create
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Activate when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on…
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
completion-verification
Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
watch-pr
Watch an Elixir/Phoenix PR for new review comments (bot + human) and CI results via a background watcher that wakes Claude only on real events. Use after opening a PR or pushing, while waiting on CI or reviewers.