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/openshift-eng/ai-helpersWrote 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/openshift-eng/ai-helpers/nudge-prs)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/nudge-prs"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/nudge-prs.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.00011 | $0.00502 |
| Opus 5 | $0.00005 | $0.00251 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
nudge-prs 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 2d 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
Name
nid-team:nudge-prs
Synopsis
/nid-team:nudge-prs [--dryrun] [--days 7] [--priority High,Urgent]
Description
Sends automated reminder comments on PRs that are assigned (Status=Assigned), high priority (PR Priority=High or Urgent), and have had no human activity for a configurable number of days.
Implementation
Run the nudge script:
plugins/nid-team/scripts/pr-dashboard/nudge-prs.sh [--dryrun] [--days 7] [--priority High,Urgent]
Arguments
| Argument | Default | Description |
|---|---|---|
--dryrun |
off | Print the comments without posting them |
--days |
7 | Days of inactivity threshold |
--priority |
High,Urgent | Comma-separated PR Priority values to nudge |
What counts as human activity
- Author pushed commits
- Human review comment (not CodeRabbit or bots)
- Human PR comment (not bots, not Prow commands like /assign /label /hold)
Bot comments and mechanical Prow commands do NOT reset the inactivity clock.
What the comment includes
- How long the PR has been open
- Author and Reviewer @-mentions
- Last human activity (who and when)
- needs-rebase and do-not-merge/hold warnings
- lgtm/approved label status
Examples
# Dry run — see what would be posted
/nid-team:nudge-prs --dryrun
# Post reminders for High and Urgent PRs inactive 7+ days
/nid-team:nudge-prs
# Custom threshold — 14 days, all priorities
/nid-team:nudge-prs --days 14 --priority High,Urgent,Medium
Notes
- Only nudges PRs with Status=Assigned on the dashboard
- Always use
--dryrunfirst to review the comments before posting - Does not nudge the same PR twice per run (idempotent within a run)
- Does not track previous nudges — running it again will post another comment
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.
- 2d ago First seen · 71 lines · 11 tokens per session scan A d698e29382bc
nudge-prs is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 3d ago), licensed Apache-2.0. It adds 11 tokens to every session and 502 once invoked, about $0.0001 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-05.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.