Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/quay/ai-helpersnpx agentmods add skills/quay/ai-helpers/pollWrote 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/quay/ai-helpers/poll)<a href="https://agentmods.dev/skills/quay/ai-helpers/poll"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/poll.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.00055 | $0.00887 |
| Opus 5 | $0.00028 | $0.00443 |
| Sonnet 5 | $0.00011 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
poll 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 yesterday.
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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Poll PR and Act on Feedback
Poll PR #$ARGUMENTS for CI, CodeRabbit, and human review status, then fix what's broken.
The script manages its own state in .claude/poll-state/pr-$ARGUMENTS.json and loops
internally with adaptive backoff (120-600s). It shows a full report on the first run,
then delta-only on subsequent polls so only new events surface.
CRITICAL: always use run_in_background: true
Run the script via the Bash tool with run_in_background: true. Never use & to
background it in the shell — that detaches the process and makes the exit code invisible.
# Bash tool call — set run_in_background: true
bash .claude/scripts/poll-pr.sh $ARGUMENTS
The script sleeps and polls on its own. Do not interrupt it. When it exits, you will be notified automatically.
Exit codes — what to do when notified
| Code | Meaning | Action |
|---|---|---|
| 0 | All checks pass | Ready to merge |
| 1 | CI failures | Fix code, push, re-run (background again) |
| 2 | Checks pending | Should not exit 2 unless --max-polls hit; re-run |
| 3 | Inline review comments | Address comments, push, re-run (background again) |
| 4 | Awaiting human review | Reviewer team notified; CronCreate to re-poll later |
Exit 4 — schedule a re-poll cron
When the script exits 4, it has already posted a comment and requested reviewers. Use CronCreate to check back automatically:
CronCreate: every 2 hours, /poll $ARGUMENTS
Delete the cron (CronDelete) once the PR is approved or merged.
Exit 1 — CI failures
Run the relevant test/lint commands per the project's AGENTS.md to reproduce
and fix failures locally. After fixing: push, then re-run the script via Bash
with run_in_background: true.
Exit 3 — inline review comments
Run --once --full to see comments with reply/resolve commands:
bash .claude/scripts/poll-pr.sh $ARGUMENTS --once --full
Evaluate each comment critically — automated reviewers are often right but not always. Read the full context, understand what it's flagging, and make a genuine judgment call:
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.
- yesterday First seen · 108 lines · 55 tokens per session scan A 96c872662b7d
poll is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 55 tokens to every session and 887 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-09-04.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.