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 commands/edutrul/drupal-ai/review-prgit 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/review-pr)<a href="https://agentmods.dev/commands/edutrul/drupal-ai/review-pr"><img src="https://agentmods.dev/badge/commands/edutrul/drupal-ai/review-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.00058 | $0.02305 |
| Opus 5 | $0.00029 | $0.01153 |
| Sonnet 5 | $0.00012 | $0.00461 |
| Haiku 4.5 | $0.00006 | $0.00231 |
Grade B, and why
review-pr 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 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.
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 auth status:), Bash(gh auth switch:), Bash(gh pr view:), Bash(gh pr diff:), Bash(gh pr comment:), Bash(gh pr review:), Bash(git fetch:), Bash(git checkout:), Bash(git pull:), Bash(git stash:), Bash How it starts
The opening of the file, as written. The whole thing — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PR
Prepare a GitHub Pull Request locally, analyze it using project rules, optionally post a GitHub review comment, and optionally synchronize the related Jira ticket.
Purpose
Use this command when the user provides a PR URL or number and wants to:
- prepare PR locally
- review code using project standards
- generate a review summary
- optionally post a GitHub comment
- optionally update Jira based on review outcome
Input
- GitHub PR URL or number
If missing → ask for it.
Assumptions
- Inside correct repo
- Uses GitHub (
gh) - Uses DDEV + Drupal
- Uses Jira via
acli - Mappings at
.claude/data/mappings.json
Workflow
1. Validate GitHub access
Run:
gh auth status
If fails:
gh auth switch --user <account>
2. Resolve PR details
Run:
gh pr view <number-or-url> --json headRefName,title,files,author,body
Show:
- title
- branch
- changed files
3. Detect Jira ticket
Search in:
- PR title
- body
- branch
Example: PRJ-703
If none found:
- continue without Jira
4. Ensure DDEV running
Run:
ddev describe || ddev start
5. Checkout branch
Run:
git fetch origin
git checkout -b <branch_name> origin/<branch_name>
If exists:
git checkout <branch_name>
git pull origin <branch_name>
If blocked → ask to stash.
6. Prepare environment
Run:
composer install
drush cim -y
drush updb -y
drush cr
Stop on failure.
7. Generate login link
Run:
ULI=$(drush uli) && echo "$ULI" && open "$ULI"
8. Run PHPCS on changed files
From the changed files list gathered in step 2, filter to PHP files that fall within PHPCS scope:
docroot/modules/custom/docroot/themes/custom/docroot/sites/default/settings.php
For each matching file, run:
phpcs <file-path>
Collect all output. If no PHP files are in scope, skip this step silently.
Store the raw PHPCS output — it will be used directly in the Analysis Phase.
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 · 424 lines · 58 tokens per session scan B 425294578fc0
review-pr is a command published in the GitHub repository edutrul/drupal-ai (71 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 2,305 once invoked, about $0.0003 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
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
synthesise-reviews
Deduplicate and reconcile multiple completed review reports into one prioritised revision plan with conflicts and dependencies made explicit. Use when parallel reviewers have returned findings that need a single action sequence. Not for running the reviews; use $review-cluster.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.