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-merge-pr)<a href="https://agentmods.dev/commands/ddgonzal3/rally/rally-merge-pr"><img src="https://agentmods.dev/badge/commands/ddgonzal3/rally/rally-merge-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/ddgonzal3/rally/rally-merge-pr"><img src="https://agentmods.dev/badge/commands/ddgonzal3/rally/rally-merge-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.00582 |
| Opus 5.5 | $0.00000 | $0.00233 |
| Sonnet 5.5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
rally-merge-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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge PR: Merge, Sync, Stay on Feature Branch
You are merging the current branch's PR and syncing the feature branch with main. 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"
PR_NUM=$(gh pr view --json number -q '.number' 2>/dev/null)
echo "BRANCH=$BRANCH MAIN=$MAIN_BRANCH PR=$PR_NUM"
Guard rails:
- If
BRANCHequalsMAIN_BRANCH, STOP: "You're on the main branch. Switch to the feature branch whose PR you want to merge." - If
PR_NUMis empty, STOP: "No PR found for this branch. Create a PR first."
Step 2: Verify PR is Mergeable
MERGEABLE=$(gh pr view "$PR_NUM" --json mergeable -q '.mergeable')
echo "MERGEABLE=$MERGEABLE"
If MERGEABLE=CONFLICTING, STOP: "PR has merge conflicts. Resolve them before merging."
Step 3: Merge the PR
Merge with squash. Do NOT delete the remote branch.
gh pr merge "$PR_NUM" --squash
Step 4: Sync Feature Branch
After the merge is complete, sync the local environment:
# 1. Update main with the merged changes
git checkout "$MAIN_BRANCH"
git pull
# 2. Go back to the feature branch
git checkout "$BRANCH"
# 3. Count commits ahead of main (these were squash-merged, now redundant)
AHEAD=$(git rev-list --count "$MAIN_BRANCH".."$BRANCH")
echo "Commits to reset: $AHEAD"
# 4. Reset the redundant commits and rebase onto main
if [ "$AHEAD" -gt 0 ]; then
git reset --hard "HEAD~$AHEAD"
fi
git rebase "$MAIN_BRANCH"
# 5. Push the synced branch to keep remote in sync
git push --force-with-lease
Step 5: Final Output
Print a summary:
- PR number and URL that was merged
- Branch that was synced
- Current state: on
BRANCH, synced withMAIN_BRANCH
Example:
Merged PR #42 (squash) into main.
Synced feature-branch with main (reset 3 commits, rebased).
Currently on: feature-branch (synced with main)
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 · 76 lines · 0 tokens per session scan A 3207017397e5
rally-merge-pr is a command published in the GitHub repository ddgonzal3/rally (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 582 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
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
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.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
doc-changelog
Generation and maintenance of the project changelog.