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/ddgonzal3/rallyWrote 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/ddgonzal3/rally/rally-create-pr)<a href="https://agentmods.dev/commands/ddgonzal3/rally/rally-create-pr"><img src="https://agentmods.dev/badge/commands/ddgonzal3/rally/rally-create-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.1 | $0.00000 | $0.00771 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
rally-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 8d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR: Branch (if needed), Push, and Open PR
You are creating a pull request for the current working changes. Follow each step exactly.
Step 1: Detect State
BRANCH=$(git symbolic-ref --short HEAD)
MAIN_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')
[ -z "$MAIN_BRANCH" ] && MAIN_BRANCH="main"
IS_DIRTY=$([ -n "$(git status --porcelain)" ] && echo "true" || echo "false")
EXISTING_PR=$(gh pr view --json number,state -q 'select(.state=="OPEN") | .number' 2>/dev/null)
echo "BRANCH=$BRANCH MAIN=$MAIN_BRANCH DIRTY=$IS_DIRTY EXISTING_PR=$EXISTING_PR"
Guard rail: If EXISTING_PR is not empty, STOP: "PR #$EXISTING_PR already exists for this branch. Push new commits to update it, or use /review-pr to review it."
Step 2: Create Feature Branch (if on main)
If BRANCH equals MAIN_BRANCH:
- Inspect the working tree to understand the changes:
git diff --stat git diff --cached --stat git status --porcelain - Generate a short, descriptive kebab-case branch name based on the changes (e.g.,
add-user-auth,fix-sidebar-layout,update-ship-command). If there are no changes to inspect, use the surrounding conversation context. - Create and switch to the branch:
git checkout -b <generated-branch-name> - Update:
BRANCH=<generated-branch-name>
Step 3: Commit if Dirty
Only if IS_DIRTY=true:
-
Read the diff to understand what changed:
git diff --stat git diff --cached --stat -
Write a concise, descriptive commit message based on the diff:
git add -A git commit -m "<your descriptive message>"
If the working tree is clean and there are no new commits beyond main, STOP: "Nothing to create a PR for — no changes found."
Step 4: Push
git push 2>/dev/null || git push --set-upstream origin "$BRANCH"
Step 5: Analyze Changes and Create PR
Read the full diff against main to write a good PR description:
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.
- 8d ago First seen · 104 lines · 0 tokens per session scan A d1a35f16fb34
rally-create-pr is a command published in the GitHub repository ddgonzal3/rally (6 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 771 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-31.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.