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 skills/dburkart/auto-engineer/wait-for-prnpx skills add dburkart/auto-engineer --skill wait-for-prgit clone --depth 1 https://github.com/dburkart/auto-engineerWrote 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/dburkart/auto-engineer/wait-for-pr)<a href="https://agentmods.dev/skills/dburkart/auto-engineer/wait-for-pr"><img src="https://agentmods.dev/badge/skills/dburkart/auto-engineer/wait-for-pr.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.00053 | $0.01237 |
| Opus 5 | $0.00026 | $0.00619 |
| Sonnet 5 | $0.00011 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
wait-for-pr 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wait-for-pr
Read docs/agent-playbooks/pr-review.md first for repo-level CI readiness and review-classification rules.
This skill keeps only the Claude-specific wait loop and automation needed to turn shared review rules into a single consolidated PR-status report.
When to invoke
- Immediately after
gh pr create/mcp__github__create_pull_requestreturns a PR URL. - After pushing a follow-up commit to a PR branch (re-enter the loop to confirm green).
- When the user says "wait for CI," "check the PR," or similar.
Identifying the PR
If the PR number isn't already known from the preceding tool call:
gh pr list --head "$(git branch --show-current)" --json number,url --jq '.[0]'
Record the number and URL; reuse them for every poll tick.
What "done" means
The PR isn't ready for a summary until all are true:
- Every GitHub Actions check is in a terminal state:
success,failure,skipped,cancelled,neutral,timed_out, orstale. Nothingin_progress,queued, orpending. - No check is sitting in
action_requiredwaiting on manual approval (flag it and stop — the user needs to act). - At least one review-bot comment / review exists, or 30 minutes have elapsed since the PR opened (bots may not be wired up; don't block forever).
Poll cadence
Use ScheduleWakeup between ticks. Tune delaySeconds to stay friendly to the 5-minute prompt-cache TTL:
| Elapsed since PR opened | delaySeconds |
|---|---|
| 0–10 min | 120 |
| 10–30 min | 180 (still under the 270 s cache window) |
| 30 min+ (waiting only on slow bots) | 1200 |
Never pick 300 s — it's the worst of both worlds (cache miss with no payoff). Under 10 minutes, stay ≤ 270 s.
Each poll tick
-
Check CI state:
gh pr checks <PR> --json name,state,bucket,linkor
mcp__github__get_pull_request_status. -
Count review-bot activity:
gh api "repos/dburkart/auto-engineer/issues/<PR>/comments" \ --jq '[.[] | select(.user.login | test(""))] | length'Also fetch formal reviews via
mcp__github__get_pull_request_reviews.
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 · 127 lines · 53 tokens per session scan A c83dfced2ed2
wait-for-pr is a skill published in the GitHub repository dburkart/auto-engineer (5 stars, last pushed 4mo ago), licensed BSD-3-Clause. It adds 53 tokens to every session and 1,237 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…