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/areal-project/areal/create-prgit clone --depth 1 https://github.com/areal-project/AReaLWhat 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.00040 | $0.05611 |
| Opus 5 | $0.00020 | $0.02805 |
| Sonnet 5 | $0.00008 | $0.01122 |
| Haiku 4.5 | $0.00004 | $0.00561 |
Grade A, and why
create-pr 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 796 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Rebase from the latest origin/main, squash commits, and create a PR on GitHub with an
intelligent title and description.
Usage
/create-pr [--draft] [--base <branch>]
Arguments:
--draft: Create as draft PR--base <branch>: Target branch (default:main)
Workflow
Step 1: Verify Prerequisites
# Check current branch
git branch --show-current
# Check if on main/master (should NOT be)
if [[ $(git branch --show-current) == "main" || $(git branch --show-current) == "master" ]]; then
echo "ERROR: Cannot create PR from main/master branch"
exit 1
fi
# Check for uncommitted changes
git status --short
# Ensure gh CLI is available
gh --version
Action: If there are uncommitted changes, stop, and then ask user to commit or stash them first.
Step 1.5: Determine Push Remote (Fork Support)
Check if user has push access to origin, and if not, identify the fork remote.
# List all remotes
git remote -v
# Try to determine push remote
# Option 1: Check if origin is writable (try a dry-run push)
git push --dry-run origin $(git branch --show-current) 2>&1
# Option 2: Check gh auth status and repo permissions
gh auth status
gh repo view --json owner,name,viewerPermission
Logic for Determining Push Remote:
If origin is writable: Use origin directly (maintainer workflow)
If origin is NOT writable: Look for a fork remote
- Common fork remote names:
fork,user,<username>, or any remote pointing to user's fork - Verify the fork remote points to user's own fork via
gh repo view <remote-url> --json owner
If no fork remote found: Ask user to add their fork as a remote:
git remote add fork https://github.com/<username>/AReaL.git
Store for later use:
PUSH_REMOTE: The remote to push to (e.g.,originorfork)UPSTREAM_REPO: The upstream repo for PR target (e.g.,areal-project/AReaL)FORK_OWNER: Fork owner username (for--headparameter if needed)
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.
- 3d ago First seen · 796 lines · 40 tokens per session scan A b29389596e2a
create-pr is a command published in the GitHub repository areal-project/AReaL (5,708 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 5,611 once invoked, about $0.0002 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-08-30.
Other commands, from other repositories
commit-message
Suggest a clear and simple commit message for the current changes.
simplify-comments
Review the comments in a given range and cut them down to only what is needed.
commit-push-pr
Commit, push, and open a PR.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.