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/hmaurus/masterclaude/pdir-merge-prgit clone --depth 1 https://github.com/hmaurus/masterclaudeWrote 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/hmaurus/masterclaude/pdir-merge-pr)<a href="https://agentmods.dev/commands/hmaurus/masterclaude/pdir-merge-pr"><img src="https://agentmods.dev/badge/commands/hmaurus/masterclaude/pdir-merge-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.00026 | $0.00708 |
| Opus 5 | $0.00013 | $0.00354 |
| Sonnet 5 | $0.00005 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
pdir-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 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PDIR: Merge PR
Valida, faz o squash merge do PR e limpa a branch local/remota.
Pré-requisito: PR aprovado e pronto para merge.
Em qualquer passo, se algo falhar ou faltar informação, informe o erro e pergunte ao usuário como prosseguir.
Descobrir o PR
- Com argumento (
$ARGUMENTS): número do PR (descarte o#se vier). - Sem argumento: use o PR aberto da branch atual.
Leia o PR com gh pr view <número> --json number,title,state,isDraft,headRefName e mostre número + título — é a conferência de que você vai mergear o PR certo. Um squash merge com --delete-branch é irreversível na prática (some com a branch). Se o PR não estiver aberto (já mergeado/fechado) ou for draft, pare e avise — não faça merge.
Instruções
1. Validar localmente
Rode os checks do projeto (lint, type-check, build) — consulte package.json, Makefile ou equivalente para os comandos disponíveis. Se algum falhar, pare e informe ao usuário.
2. Verificar o CI do PR
Cheque o status dos checks de CI do PR (gh pr checks <número>). Se houver algo falhando, pare e pergunte se o usuário quer aguardar, seguir mesmo assim, ou abortar.
3. Fazer o merge
Guarde o nome da branch de origem do PR — o headRefName que você leu ao descobrir o PR. Precisa dele para a limpeza, e a branch pode sumir logo em seguida.
Faça o squash merge deletando a branch:
gh pr merge <número> --squash --delete-branch
O --squash (convenção do PDIR: um commit por PR) e o --delete-branch (remove a branch remota — e a local, se você estiver nela) são intencionais — mantenha ambos.
4. Sincronizar o local
Volte para o branch default e atualize-o:
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef -q .defaultBranchRef.name)
git checkout "$DEFAULT_BRANCH"
git pull origin "$DEFAULT_BRANCH"
O passo anterior já removeu a branch de origem remota (e a local, se você estava nela). Se a branch local ainda existir, remova-a com git branch -d <headRefName>. O -d recusa apagar trabalho não mergeado — se ele reclamar, não force com -D: investigue por que a branch parece não mergeada.
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 · 69 lines · 26 tokens per session scan A 3ac172cc71fb
pdir-merge-pr is a command published in the GitHub repository hmaurus/masterclaude (2 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 708 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-08-31.
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.