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/create-pr)<a href="https://agentmods.dev/commands/edutrul/drupal-ai/create-pr"><img src="https://agentmods.dev/badge/commands/edutrul/drupal-ai/create-pr/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/create-pr"><img src="https://agentmods.dev/badge/commands/edutrul/drupal-ai/create-pr.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.00035 | $0.00755 |
| Opus 5.5 | $0.00014 | $0.00302 |
| Sonnet 5.5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade B, and why
create-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 1mo 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(git branch --show-current:), Bash(git log *:), Bash(git push *:), Bash(gh pr create:), Bash(gh pr view:), Bash(acli jira auth status:), Bash(acli jira workitem view:), Bash(acli jira workitem transiti How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Create a Pull Request from the current branch targeting develop, following project conventions.
Input
No arguments required. Operates on the current branch.
Workflow
1. Get current branch
git branch --show-current
Detect the Jira ticket from the branch name (e.g. PRJ-356-lucidworks-indexing-endpoints → PRJ-356).
If no ticket detected → ask the user for the ticket ID before continuing.
2. Get recent commits for context
git log origin/develop..HEAD --oneline
Use commit messages to understand the scope of the PR.
3. Push branch if needed
Check if the branch has a remote tracking branch. If not:
git push -u origin <branch>
4. Single ask — PR details
Display detected info and ask once:
Branch: Jira ticket:
PR title: (pre-filled as
PRJ-XXX: <description inferred from commits>) PR description: (leave blank to auto-generate from commits, or type your own) Create as draft? (Y/n)
- If user accepts the pre-filled title → use it
- If user edits → use their version
- Default is draft (
Y)
5. Create the PR
gh pr create \
--base develop \
--title "<title>" \
--body "<body>" \
--draft
PR body template:
## Summary
<bullet points from commit messages>
## Jira
<ticket-url>
## Test plan
- [ ]
If user chose not to draft → omit --draft.
6. Jira auth check
acli jira auth status
If fails → skip Jira steps silently, list as manual action in summary.
7. Move Jira ticket to In Progress (if not already)
acli jira workitem view <ticket>
If current status is not In Progress → transition it:
acli jira workitem transition --key <ticket> --status "In Progress"
If already In Progress → skip silently.
8. Final summary
| Action | Result |
|---|---|
| Branch pushed | ✓ / already up to date |
| PR created | # — |
| Draft | yes / no |
| Jira ticket | |
| Jira status | In Progress / skipped (reason) |
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.
- 1mo ago First seen · 146 lines · 35 tokens per session scan B 94065d121a38
create-pr is a command published in the GitHub repository edutrul/drupal-ai (72 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 755 once invoked, about $0.0001 per session on Opus 5.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
ia-document-release
Post-ship documentation sync. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, and optionally bumps the version.
ia-review
Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees.
prune-sync-log
Prune stale entries from the whetstone sync decision log.
ia-changelog
Create engaging changelogs for recent merges to main branch.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.
prepr
Prepara los cambios como Pull Request listo para review.