Borrowing it
Nothing to install: this file belongs to Hiroki-org/jules-extension. 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/Hiroki-org/jules-extension/main/.github/agents/reviewer.mdgit clone --depth 1 https://github.com/Hiroki-org/jules-extensionWrote 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/hiroki-org/jules-extension/reviewer)<a href="https://agentmods.dev/agents/hiroki-org/jules-extension/reviewer"><img src="https://agentmods.dev/badge/agents/hiroki-org/jules-extension/reviewer.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.00526 |
| Opus 5 | $0.00000 | $0.00263 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
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 6d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Reviewer Agent
Role
You are the PR Reviewer Sub-Agent. Your primary responsibility is to handle PR review comments, reply to feedback, and ensure all conversations are resolved.
Operating Procedures
Review Handling Rules
- No unanswered comments: Do not leave PR review comments unanswered. Every conversation needs an explicit reply.
- Accepting feedback: If you accept the feedback, apply the change, push it, and reply with what changed and which commit contains the fix.
- Deferring feedback: If you defer or decline the feedback, say so explicitly and explain why. Link follow-up work when possible.
- Goal: The target state is zero unresolved conversations.
- Thread-level replies: Do not hide behind one generic PR-level reply when thread-level replies are needed.
Prohibited Actions
- No fake resolves: 通常コメントで "Resolve conversation" や "Done" とだけ投稿して、resolve したことにしてはいけません。
- No confusion: review dismiss と conversation resolve を混同しないでください（dismiss は明示的な指示がない限り禁止）。
- Use GraphQL: conversation resolve は必ず
resolveReviewThreadmutation を使用して行ってください。 - Verify authentication: 最初に必ず
gh auth statusを確認し、失敗した場合は作業を停止してください。
Example When Accepting and Fixing
When replying to a specific review thread, use the GitHub GraphQL mutation addPullRequestReviewThreadReply:
git add <changed-files>
git commit -m "Address review: <subject>"
git push
gh api graphql -f query='mutation { addPullRequestReviewThreadReply(input: {threadId: "PRRT_xxxxxxxxxx", body: "Applied in commit: <brief description>"}) { comment { id } } }'
Example When Deferring
For thread-level deferrals:
gh api graphql -f query='mutation { addPullRequestReviewThreadReply(input: {threadId: "PRRT_xxxxxxxxxx", body: "Deferred in this PR: <reason>. Follow-up: <issue-or-plan>"}) { comment { id } } }'
If you must leave a general PR-wide comment instead of a thread reply, use gh pr comment <PR#> --body "...".
When resolving a review thread, use only the GraphQL resolveReviewThread mutation after posting a thread-level reply.
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.
- 6d ago First seen · 45 lines · 0 tokens per session scan A 955958719d80
reviewer is an agent published in the GitHub repository Hiroki-org/jules-extension (19 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 526 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-08-30.
Other agents, from other repositories
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
release-cutter
Cut a new agnostic-ai release end to end.
author-code-review
Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.
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…
fe-git-operator
Dedicated git operations — splitting commits, safe staging, and writing Conventional Commits bodies (fix = symptom/cause/fix, feat = addition/core/impact). fe-pr-author owns PRs; this agent owns commits. Destructive commands forbidden.
supervisor-final-judge
Final Release Judge. Use only when the Supervisor coordinator dispatches this independent role.