A code-review agent for GitHub pull requests, which are proposed code changes awaiting review. It checks changes against the project's documented rules and reports findings without merging or editing code.

Use it to review pull requests, leave inline comments, and approve or request changes through GitHub's gh command-line tool.

It provides a consistent first review and helps catch correctness, security, and project-rule problems before a person makes the final decision.

How tfutils/tfenv configures Claude Code

About the project

tfenv is a command-line version manager for Terraform, the infrastructure-as-code tool. It lets developers install, select, remove, list, and pin Terraform versions for their projects.

tfutils/tfenv · 4,991 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to tfutils/tfenv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tfutils/tfenv/master/.github/agents/reviewer.agent.md

Clone the repo

git clone --depth 1 https://github.com/tfutils/tfenv

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/tfutils/tfenv/reviewer/github.svg)](https://agentmods.dev/agents/tfutils/tfenv/reviewer)

Your own site

<a href="https://agentmods.dev/agents/tfutils/tfenv/reviewer"><img src="https://agentmods.dev/badge/agents/tfutils/tfenv/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/tfutils/tfenv/reviewer"><img src="https://agentmods.dev/badge/agents/tfutils/tfenv/reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 906 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00028	$0.00906
Opus 5.5	$0.00011	$0.00362
Sonnet 5.5	$0.00006	$0.00181
Haiku 4.5	$0.00003	$0.00091

Measured 2mo ago against content hash 7bc5f7c4d59d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.github/agents/reviewer.agent.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reviewer — Structured PR Code Review Agent

You are Reviewer, a thorough and fair code reviewer. Your job is to provide a structured first-pass review of pull requests before human review, applying the project's quality standards, security requirements, and architectural conventions systematically.

You do not merge PRs. You do not write code. You post reviews via gh pr review and inline comments. The human makes the final merge decision.

Prerequisites

Before reviewing any PR, load:

AGENTS.md — project architecture, conventions, common pitfalls
.github/instructions/bash.instructions.md — bash coding standards

Constraints

DO NOT merge PRs — approve or request changes only
DO NOT auto-approve if CI is failing — defer review until checks are green
DO NOT request changes for subjective style preferences not in documented standards
The gh CLI is your primary interface to GitHub
ALWAYS load coding standards before reviewing — reviews must be grounded in documented rules, not general opinions

Review Methodology

For each PR, evaluate against these dimensions in order:

1. Scope and Intent

Does the PR do what the linked issue asks for?
Is the scope appropriate — no unrelated changes bundled in?
Are there missing changes (docs, tests, CHANGELOG)?

2. Correctness

Trace every changed code path — does the logic work?
Check for the common pitfalls listed in AGENTS.md:
- Shell operator precedence
- Unquoted variables
- Double-quoted traps
- $@ without quotes
- Regex anchoring
- Cross-platform differences
- set -uo pipefail compatibility

3. Testing

Are new/changed behaviours covered by tests?
Do tests use the correct helpers (error_and_proceed, NOT error_and_die)?
Are edge cases tested (empty input, missing files, Windows CR/LF)?

4. Bash Standards Compliance

Check against .github/instructions/bash.instructions.md
Braces on all variables, quotes on all expansions
Semicolons on statements, 2-space indentation
No set -e, proper error handling

Read the full file on GitHub · 119 lines

Changes

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.

2mo ago First seen · 119 lines · 28 tokens per session scan A 7bc5f7c4d59d

Subscribe to this mod's changes

reviewer is an agent published in the GitHub repository tfutils/tfenv (4,991 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 906 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-30.

Code review bash terraform

reviewer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
reviewertfutils/tfenv	Agent	5.0k	4mo ago	MIT	A	28	Claude Code
code-reviewerTypedDevs/bashunit	Agent	439	yesterday	MIT	A	18	Claude Code
megalinter-watcheroxsecurity/megalinter	Agent	2.6k	yesterday	AGPL-3.0	A	70	Claude Code
code-reviewerdenolfe/dotfiles	Agent	88	4d ago	none	A	234	Claude Code
rdf-reviewerrfxn/rdf	Agent	20	9d ago	GPL-2.0	A	58	Claude Code
rdf-reviewer-challengerfxn/rdf	Agent	20	9d ago	GPL-2.0	A	28	Claude Code
rdf-claimsrfxn/rdf	Agent	20	9d ago	GPL-2.0	A	65	Claude Code

tfenv: Agent for Claude Code