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/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-criar-pr)<a href="https://agentmods.dev/commands/hmaurus/masterclaude/pdir-criar-pr"><img src="https://agentmods.dev/badge/commands/hmaurus/masterclaude/pdir-criar-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/hmaurus/masterclaude/pdir-criar-pr"><img src="https://agentmods.dev/badge/commands/hmaurus/masterclaude/pdir-criar-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.00026 | $0.01062 |
| Opus 5.5 | $0.00010 | $0.00425 |
| Sonnet 5.5 | $0.00005 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
pdir-criar-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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PDIR: Criar PR
Cria um Pull Request vinculado a uma Issue, validando antes e padronizando o corpo.
Pré-requisitos: estar numa branch de feature (não no branch default) com os commits já feitos.
Em qualquer passo, se algo falhar ou faltar informação, informe o erro e pergunte ao usuário como prosseguir.
Descobrir a Issue
- Com argumento (
$ARGUMENTS, ex:42ou#42): use os dígitos (descarte o#). - Sem argumento: pegue o trecho entre a primeira
/e o próximo-(ou o fim do nome, se não houver-). Use como número da Issue somente se esse trecho for inteiramente dígitos.feat/42-login→ trecho42→#42✓feat/42→ trecho42→#42✓feat/login-oauth2→ trechologin→ perguntafeat/2fa-login→ trecho2fa→ pergunta (não é só dígito)
Não adivinhe. Se o trecho não for inteiramente numérico, não pesque um dígito de dentro do slug — pergunte ao usuário qual é a Issue. Um número errado aqui vira Closes #N e fecha a Issue errada no merge.
Instruções
1. Verificar estado
Descubra o branch default do repositório com gh repo view --json defaultBranchRef -q .defaultBranchRef.name (não assuma main — pode ser master/develop); reuse esse valor nos passos seguintes.
Confirme, via git, que você não está no branch default e que não há mudanças não commitadas. Se estiver no default, encerre informando o motivo. Se houver pendências não commitadas, avise e sugira commitar primeiro (é só pedir "commit").
2. Validar
Rode os checks do projeto (lint, type-check, testes) — consulte package.json, Makefile ou equivalente para os comandos disponíveis. Se algum falhar, informe e pergunte se o usuário quer corrigir antes ou seguir mesmo assim. Validar antes do push evita disparar CI em código sabidamente quebrado.
3. Publicar a branch
Faça push da branch para o origin. Se ela ainda não tiver upstream, configure-o no push (-u); se já tiver, envie só os commits pendentes.
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 · 85 lines · 26 tokens per session scan A 98c1b1cd6430
pdir-criar-pr is a command published in the GitHub repository hmaurus/masterclaude (2 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 1,062 once invoked, about $0.0001 per session on Opus 5.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
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-tag
Create and push a version tag after a release PR has been merged.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.