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/edutrul/drupal-aiWrote 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/edutrul/drupal-ai/ready-pr-in-review)<a href="https://agentmods.dev/commands/edutrul/drupal-ai/ready-pr-in-review"><img src="https://agentmods.dev/badge/commands/edutrul/drupal-ai/ready-pr-in-review/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/commands/edutrul/drupal-ai/ready-pr-in-review"><img src="https://agentmods.dev/badge/commands/edutrul/drupal-ai/ready-pr-in-review.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.00037 | $0.01353 |
| Opus 5 | $0.00018 | $0.00677 |
| Sonnet 5 | $0.00007 | $0.00271 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade B, and why
ready-pr-in-review scanned grade B with 1 finding 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 10d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
allowed-tools: Bash(gh pr list:), Bash(gh pr view:), Bash(gh pr ready:), Bash(gh pr edit:), Bash(gh label list:), Bash(gh label create:), Bash(acli jira auth status:), Bash(acli jira workitem view:), Bash(acli jira worki How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Put PR in Review
Prepares a Pull Request for technical review and synchronizes the related Jira ticket.
Input
- PR URL or PR number
If not provided → run
gh pr list --json number,title,isDraft,headRefNameand ask.
Workflow
1. Identify and display the PR
gh pr view <number-or-url> --json number,title,isDraft,headRefName,body,url,author
Display:
- PR number, title, branch
- Draft status
- Author
- Jira ticket (detected from title, body, or branch — e.g.
PRJ-703)
2. Single ask — reviewer + labels
First, load the mappings:
cat .claude/data/mappings.json
Build a numbered list from github_to_jira entries, excluding the PR author.
Format each entry as: <N>. <name> (@<github-username>)
Ask once:
PR # —
Who is the code reviewer? [numbered list from mappings, author excluded] (or type a different GitHub username)
Any labels to add? (leave blank to skip — common:
backend,frontend,bug,enhancement,drupal)
If reviewer picks a number → resolve to that GitHub username automatically. If labels are left blank → skip label steps entirely, do not ask again.
3. Move PR to Ready for Review
If PR is Draft:
gh pr ready <number-or-url>
If already ready → skip silently.
4. Assign reviewer in GitHub
gh pr edit <number-or-url> --add-reviewer "<github-username>"
5. Add labels (only if provided in step 2)
Check existing labels:
gh label list
Create any missing ones:
gh label create "<label>" --color "84b6eb"
Assign:
gh pr edit <number-or-url> --add-label "<label>"
6. Jira auth check
acli jira auth status
If fails → skip all Jira steps silently, list them as manual actions in the final summary.
Do not ask the user to log in. To fix outside this command: acli jira auth login
7. Verify Jira ticket
acli jira workitem view <ticket>
If ticket not found → skip Jira steps, report in summary.
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.
- 10d ago First seen · 222 lines · 37 tokens per session scan B 35459684bf2e
ready-pr-in-review is a command published in the GitHub repository edutrul/drupal-ai (71 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,353 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
gsd:complete-milestone
Archive completed milestone and prepare for next version.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
ia-changelog
Create engaging changelogs for recent merges to main branch.
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable. Not Done until Phase 5 exit checklist passes.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.
release
Generate changelog, bump version, and create git tag.