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/rootstrap/rails_api_base/create-prgit clone --depth 1 https://github.com/rootstrap/rails_api_baseWhat 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.00000 | $0.00347 |
| Opus 5 | $0.00000 | $0.00173 |
| Sonnet 5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
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 yesterday.
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
Create PR
Create a pull request following the official template.
For PR content guidance, see .claude/rules/github-pr-formatting.md
Workflow
1. Check PR Size
Before anything else, run the pr-size-checker agent to analyze the diff size.
- If the agent recommends splitting, present the split plan to the user and ask how they'd like to proceed
- Only continue with PR creation after the user confirms (either to proceed as-is or after splitting)
2. Prepare Branch
- Check for uncommitted changes or unpushed commits
- If found, ask user if they want to proceed (advise pushing manually due to long pre-push hooks)
3. Gather Information
# Commit log on this branch
git log main..HEAD --oneline
# Files changed
git diff main...HEAD --name-only
4. Generate PR Description
Follow .claude/rules/github-pr-formatting.md to fill each section of the template (Board, Description, Notes, Tasks, Risk, Preview).
5. Create PR
BASE_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' 2>/dev/null || echo "main")
gh pr create --title "[{TICKET-ID}] {Concise description}" --body "{BODY}" --base "$BASE_BRANCH"
If there is no associated ticket, drop the [TICKET-ID] prefix and use just the description.
6. Amend the Body if Needed
gh pr edit {PR_NUMBER} --body "{UPDATED_BODY}"
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.
- yesterday First seen · 49 lines · 0 tokens per session scan A 4b2c820397fb
create-pr is a command published in the GitHub repository rootstrap/rails_api_base (633 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 347 tokens. 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
sonicjs-pr-fixer
You are a specialized agent that helps fix and merge problematic PRs in the SonicJS repository. This includes PRs from forks that need cherry-picking, Dependabot PRs that need e2e tests enabled, and any PR that needs fixes before merging.
sonicjs-seo-blog
Generate a high-quality, SEO-optimized blog post for SonicJS on the topic: $ARGUMENTS.
templates
Manage locally-stored email templates for composing messages with variable substitution.
cli-patterns
Reference patterns for implementing CLI commands in internal/cli/.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.