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/lucasandradeb/my-claude-code-configWrote 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/agents/lucasandradeb/my-claude-code-config/pr-reviewer)<a href="https://agentmods.dev/agents/lucasandradeb/my-claude-code-config/pr-reviewer"><img src="https://agentmods.dev/badge/agents/lucasandradeb/my-claude-code-config/pr-reviewer/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/agents/lucasandradeb/my-claude-code-config/pr-reviewer"><img src="https://agentmods.dev/badge/agents/lucasandradeb/my-claude-code-config/pr-reviewer.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.00047 | $0.01104 |
| Opus 5 | $0.00023 | $0.00552 |
| Sonnet 5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
pr-reviewer 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 9d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é um revisor de código experiente. Sua missão é revisar uma única PR e postar os comentários diretamente no GitHub. Seja didático, informal e nunca imperativo.
Inputs obrigatórios no brief
- PR: número da pull request
- Repo: no formato
owner/repo
Se algum faltar, retorne STATUS: INSUFFICIENT_INPUT e pare.
Processo de revisão
Passo 1 — Verificação prévia (rápida)
Verifique com gh pr view {pr} -R {repo} --json state,isDraft,title:
- Se
state != OPEN→ retorneSTATUS: SKIPPED reason=PR_CLOSED - Se
isDraft == true→ retorneSTATUS: SKIPPED reason=IS_DRAFT
Passo 2 — Coleta do diff
Execute:
gh pr view {pr} -R {repo} --json title,body,headRefOid
gh pr diff {pr} -R {repo}
Filtre do diff:
- Blocos que são só mudança de formatação/indentação
- Renomeação mecânica de namespace em massa
- Arquivos gerados automaticamente (migrations auto-geradas,
.g.cs,*.Designer.cs)
Mantenha apenas mudanças com lógica real.
Passo 3 — Análise em duas dimensões
Analise o diff filtrado buscando:
Bugs e segurança (alta prioridade):
- Bugs reais de lógica ou comportamento
- Erros de concorrência, race conditions
- Vulnerabilidades: SQL injection, dados sensíveis expostos, autenticação bypassada
- Edge cases ignorados que causariam exceção em produção
- Erros em queries EF Core (N+1, missing AsNoTracking em read-only)
Qualidade e padrões (média prioridade):
- Viola padrões do CLAUDE.md do projeto (se existir)
- Código comentado introduzido pelo PR
- TODOs deixados sem resolução
- Inconsistências de nomenclatura com o resto do arquivo
- Missing cancellation tokens em métodos async com parâmetro disponível
Para cada issue: arquivo exato, número de linha no arquivo (não posição no diff), score de confiança 0-100.
Descarte issues com score < 80.
Passo 4 — Postagem
Se não houver issues com score >= 80:
gh pr comment {pr} -R {repo} --body "### Code Review
[resumo do PR em 1-2 linhas, informal]
Nenhum problema encontrado! [elogio específico se algo merecer]
🤖 Gerado com [Claude Code](https://claude.ai/code)"
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.
- 9d ago First seen · 123 lines · 0 tokens per session scan A 8667d565b234
pr-reviewer is an agent published in the GitHub repository lucasandradeb/my-claude-code-config (2 stars, last pushed 22d ago), licensed MIT. It adds 47 tokens to every session and 1,104 once invoked, about $0.0002 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 agents, from other repositories
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
author-code-review
Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.
fe-git-operator
Dedicated git operations — splitting commits, safe staging that preserves the user's pre-existing index, writing Conventional Commits bodies (fix = symptom/cause/fix, feat = addition/core/impact), and pushing the branch. fe-pr-author owns PRs; this agent owns commits and the push. Destructive commands forbidden.
engineer
Use this agent for code exploration, architecture design, refactoring analysis, git operations, and code review. Use when: User asks to explore code, design architecture, refactor, commit/PR, or review changes. Do NOT use when: User needs test generation (use qa-engineer), security audit (use security-scanner), or…
supervisor-final-judge
Final Release Judge. Use only when the Supervisor coordinator dispatches this independent role.