Borrowing it
Nothing to install: this file belongs to ibm-granite/granite.build. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ibm-granite/granite.build/main/.claude/commands/pr-post-merge.mdgit clone --depth 1 https://github.com/ibm-granite/granite.buildWrote 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/ibm-granite/granite.build/pr-post-merge)<a href="https://agentmods.dev/commands/ibm-granite/granite.build/pr-post-merge"><img src="https://agentmods.dev/badge/commands/ibm-granite/granite.build/pr-post-merge/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/ibm-granite/granite.build/pr-post-merge"><img src="https://agentmods.dev/badge/commands/ibm-granite/granite.build/pr-post-merge.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.00019 | $0.00763 |
| Opus 5 | $0.00010 | $0.00381 |
| Sonnet 5 | $0.00004 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
pr-post-merge 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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-merge cleanup
You are helping a developer clean up after a PR has been merged into upstream/main. Follow these steps in order.
Fork issue number: $ARGUMENTS
Step 1: Validate
-
Derive the fork owner and repo:
FORK_OWNER=$(git remote get-url origin | sed -E 's|.*[:/]([^/]+)/.*|\1|') FORK_REPO=$(git remote get-url origin | sed -E 's|.*[:/][^/]+/(.*)$|\1|' | sed 's/\.git$//') -
Detect if we are running inside a git worktree:
WORKTREE_DIR=$(git rev-parse --show-toplevel) MAIN_REPO=$(git worktree list --porcelain | head -1 | awk '{print $2}') IS_WORKTREE=false if [ "$WORKTREE_DIR" != "$MAIN_REPO" ]; then IS_WORKTREE=true; fi -
Confirm the current branch is an issue branch (not
main) -
Save the current branch name for later deletion
-
If no issue number was provided ($ARGUMENTS), try to auto-detect from the branch name:
BRANCH=$(git branch --show-current)If
$BRANCHmatches the patternissue-<N>-*, extract<N>as the issue number. Inform the user:Auto-detected issue #N from branch name
<branch>If the branch doesn't match and no
$ARGUMENTSwas given, ask the user for the issue number.
Step 2: Close the fork issue
- Close the issue in the fork repo:
gh issue close <N> --repo "$FORK_OWNER/$FORK_REPO" - Confirm the issue was closed successfully
Step 3: Update local integration branch and clean up
If running in a worktree (IS_WORKTREE=true):
The worktree must be removed before the branch can be deleted. All remaining steps run from the main repo directory.
- Change to the main repo directory:
cd $MAIN_REPO - Remove the worktree:
If removal fails (dirty worktree), ask the user whether to force-remove (git worktree remove $WORKTREE_DIRgit worktree remove --force $WORKTREE_DIR) or abort. - Update the integration branch:
git checkout main git pull upstream main - Delete the local issue branch:
git branch -d <saved-branch-name> - Delete the remote issue branch on the fork:
git push origin --delete <saved-branch-name> - Report completion to the user:
Cleaned up worktree
$WORKTREE_DIR, deleted branch<saved-branch-name>locally and on origin, updatedmain.
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.
- 5d ago First seen · 92 lines · 19 tokens per session scan A 7233580063d7
pr-post-merge is a command published in the GitHub repository ibm-granite/granite.build (44 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 763 once invoked, about $0.0001 per session on Opus 5. 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-04.
Other commands, from other repositories
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
backlog-git
Control de versiones para backlogs de proyectos.
weekly-summary
Generate weekly work summary from git activity.
gsd:pause-work
Create context handoff when pausing work mid-phase.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
afp
Prioritise feature - assigns ID, moves to backlog (shortcut for feature-prioritise).