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/rileyhilliard/rr/merge-releasegit clone --depth 1 https://github.com/rileyhilliard/rrWrote 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/rileyhilliard/rr/merge-release)<a href="https://agentmods.dev/commands/rileyhilliard/rr/merge-release"><img src="https://agentmods.dev/badge/commands/rileyhilliard/rr/merge-release.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.01264 |
| Opus 5 | $0.00000 | $0.00632 |
| Sonnet 5 | $0.00000 | $0.00253 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
merge-release 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 4d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge and Release
Automates the full release workflow: PR creation, merge, tagging, changelog update, and GitHub release.
Arguments
$ARGUMENTS: Optional version bump type (patch|minor|major). Defaults to "patch".
Pre-flight Checks
Before starting, verify:
-
Working directory state: Check for uncommitted changes
git status --porcelain- If changes exist and no recent commit in this conversation, STOP and ask user to commit first
- If we just made a commit in this conversation, proceed
-
Branch state: Determine current branch and unpushed commits
git branch --show-current git log origin/main..HEAD --oneline 2>/dev/null || git log origin/$(git branch --show-current)..HEAD --oneline- If no unpushed commits, STOP and inform user there's nothing to release
-
Get latest tags for version calculation
git tag --sort=-v:refname | head -5 -
Verify tests pass (skip if user explicitly says to skip)
make test- If tests fail, STOP and report failures
Execution Flow
Step 1: Create and Push PR
If on main with unpushed commits:
# Create feature branch from commit message
BRANCH_NAME=$(git log -1 --format=%s | sed 's/[^a-zA-Z0-9]/-/g' | tr '[:upper:]' '[:lower:]' | cut -c1-50)
git checkout -b "release/${BRANCH_NAME}"
git push -u origin "release/${BRANCH_NAME}"
Create PR:
# Get commit message for PR title
TITLE=$(git log -1 --format=%s)
gh pr create --title "$TITLE" --body "$(cat <<'EOF'
## Summary
Auto-generated release PR.
## Changes
See commit history for details.
EOF
)"
Step 2: Merge PR
# Get PR number from current branch
PR_NUMBER=$(gh pr view --json number -q .number)
gh pr merge $PR_NUMBER --squash --delete-branch
If merge fails, try rebase:
gh pr merge $PR_NUMBER --rebase --delete-branch
Step 3: Sync Local Main
git checkout main
git fetch origin
git reset --hard origin/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.
- 4d ago First seen · 194 lines · 0 tokens per session scan A 7f660cc88bde
merge-release is a command published in the GitHub repository rileyhilliard/rr (195 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,264 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-09-01.
Other commands, from other repositories
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
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
Walk the llmwiki release process step by step.
ship
Ship is the operational release-prep flow for a connected project repo.