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/rootstrap/rails_api_baseWrote 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/rootstrap/rails_api_base/create-pr)<a href="https://agentmods.dev/commands/rootstrap/rails_api_base/create-pr"><img src="https://agentmods.dev/badge/commands/rootstrap/rails_api_base/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/rootstrap/rails_api_base/create-pr"><img src="https://agentmods.dev/badge/commands/rootstrap/rails_api_base/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.00000 | $0.00347 |
| Opus 5.5 | $0.00000 | $0.00139 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 yesterday), 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
sdlc-cycle
An automated software development life-cycle (SDLC) workflow covering an issue or plan, coding, tests, verification, and a pull or merge request.
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.
discover-changelog
Given a company name or domain, find their changelog/release-note sources, add them to Releases, and fetch recent entries. This is the manual, Claude-driven onboarding flow — it uses the releases CLI against the production API and does not dispatch to managed agents. (If you want managed-agent onboarding, use releases…
ship-csk
DoD gate + commit proposal (waits for approval).
tree
Show the Tau Git Memory tree as a visual schema.
status
Run Tau Git Memory status now.