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.
git 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/commands/thettwe/nyann/wait-for-pr-checks)<a href="https://agentmods.dev/commands/thettwe/nyann/wait-for-pr-checks"><img src="https://agentmods.dev/badge/commands/thettwe/nyann/wait-for-pr-checks.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.00041 | $0.00590 |
| Opus 5 | $0.00020 | $0.00295 |
| Sonnet 5 | $0.00008 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
nyann: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 7d 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
Plugin root: This is a Claude Code plugin, NOT a CLI tool. Do NOT
search via which, npm list, pip list, or brew list. This file
is at <plugin_root>/commands/. All scripts: <plugin_root>/bin/.
Read the matching skills/*/SKILL.md for the full flow.
/nyann:wait-for-pr-checks
Wraps bin/wait-for-pr-checks.sh. Same gh-best-effort pattern as the
rest of the GitHub-touching scripts: never prompts for credentials,
soft-skips when gh is missing or unauthenticated.
| Outcome | Exit code | Meaning |
|---|---|---|
pass |
0 | every check completed with a passing conclusion |
no-checks |
0 | PR has no checks attached (treat as pass) |
skipped |
0 | gh unreachable or PR couldn't be resolved |
fail |
3 | at least one check failed; loop bailed early |
timeout |
3 | deadline reached, some still in progress |
When to invoke
- "wait for CI to finish on this PR" → run this.
- "block until checks are green before I merge" → run this, then
merge on
outcome: "pass". - "babysit the PR, ping me when it's done" → run this; the stderr log line emits per-poll progress.
When NOT to invoke
- The user wants to merge immediately when checks pass — use
/nyann:ship(server-side, doesn't tie up the terminal). - The user just wants the current status snapshot —
gh pr checks <num>directly.
See also:
/nyann:ship— combines commit, PR, and merge into a single flow./nyann:release— uses this script to gate the tag step on green checks (when invoked with--wait-for-checks).
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.
- 7d ago First seen · 56 lines · 41 tokens per session scan A 8f99e58ceaa0
nyann:wait-for-pr-checks is a command published in the GitHub repository thettwe/nyann (6 stars, last pushed 8d ago), licensed MIT. It adds 41 tokens to every session and 590 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-31.
Other commands, from other repositories
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
sdlc-release
Release planning and rollout - versioning, staging, gradual deployment, rollback.
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
gitops
Flux CD and Argo CD — two modes. debug: five structured debug workflows for live clusters (installation, source, HelmRelease, Kustomization, ResourceSet) producing a five-section report. audit: six-phase read-only repo analysis (discovery, validation, API compliance, best practices, security) producing a prioritised…
triage
Triages a PR comment — from a bot (Copilot, CI) or a human reviewer. Fetches the comment and diff via gh CLI, classifies it, applies the fix directly to the file if valid, posts a reply on the thread, and resolves it. Run from inside the repo.
genshijin-commit
A command that writes a commit message for changes already placed in Git's staging area. It follows the repository's existing language and uses a short imperative subject without AI attribution.