What is coder-eval-code-review-full?

A command for reviewing a codebase across eight critical quality areas, such as the whole project, local changes, staged files, a branch, or a pull request.

Use it to review all code, uncommitted or staged work, branch differences, unpushed commits, or a specific GitHub pull request.

It gives developers a defined review scope and a repeatable way to inspect code quality before merging or releasing changes.

coder-eval-code-review-full — Command by UiPath

Install

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.

agentmods

npx agentmods add commands/uipath/coder_eval/coder-eval-code-review-full

Clone the repo

git clone --depth 1 https://github.com/UiPath/coder_eval

Made for: Claude Code.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00008	$0.14943
Opus 5	$0.00004	$0.07472
Sonnet 5	$0.00002	$0.02989
Haiku 4.5	$0.00001	$0.01494

Measured yesterday against content hash c920883debd6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

coder-eval-code-review-full 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 yesterday.

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.

.claude/commands/coder-eval-code-review-full.md · 565 lines

How it starts

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

Context

You are performing a structured codebase review of the coder_eval project.

Optional argument: $ARGUMENTS — space-separated tokens that control review scope and axis selection. See Scope Selection below. If empty, review the full codebase across all 8 axes.

Scope Selection

$ARGUMENTS accepts a space-separated set of tokens. Default scope is all. Default axes are all 8.

Scope tokens (pick one):

all — full codebase (walk src/coder_eval/). Default.
local — uncommitted changes + untracked files. Resolve via git status --porcelain plus git diff for tracked changes; read untracked files directly.
staged — only files in git diff --staged --name-only.
branch — files changed on the current branch vs main (git diff main...HEAD --name-only).
unpushed — commits on the current branch not on origin (git log @{u}..HEAD --name-only --pretty=format: | sort -u).
pr:<N> — files in GitHub PR #N at the PR's actual HEAD, not the local working tree. The local checkout may differ from (or be unaware of) the PR's branch. Resolve as follows:
1. git fetch origin pull/<N>/head:pr-<N> — creates a local ref pr-<N> at the PR's HEAD (works for fork PRs too via the GitHub pull/<N>/head refspec).
2. gh pr view <N> --json baseRefName -q .baseRefName → store as <base>.
3. git fetch origin <base>:refs/remotes/origin/<base> — ensure base is current.
4. File list: git diff origin/<base>...pr-<N> --name-only.
5. Sub-agents read file contents via git show pr-<N>:<path>, NOT via Read on the working tree. Include this instruction in every sub-agent prompt for pr:<N> scope.

Axis filter (optional, combinable with any scope):

axis:<comma-list> — restrict to the listed axis numbers (e.g. axis:4,6).

Action flags (optional, combinable with any scope):

--post-comment — after writing the report, post 99-pr-comment.md to the relevant PR via gh pr review <N> --comment --body-file <path>. Treat this token as explicit authorization to perform the shared-state action; do not re-confirm with the user. The PR number is resolved as follows:
1. If scope is pr:<N>, use that N directly.
2. Otherwise (branch / local / staged / unpushed / all), interpret the flag as "post to this PR" — the PR associated with the current branch. Resolve via gh pr view --json number,title,author,headRefName,baseRefName,state (no arg = current branch). If that succeeds and the PR is OPEN, use its number. If gh pr view fails (no PR for the branch) or the PR is closed/merged, abort before running any tools with a clear error: "--post-comment requires either pr:<N> scope or an open PR for the current branch; got <branch> with no open PR" — and suggest pushing the branch + opening a PR first, or invoking with pr:<N> explicitly.

Read the full file on GitHub · 565 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.

yesterday First seen · 565 lines · 8 tokens per session scan A c920883debd6

Subscribe to this mod's changes

coder-eval-code-review-full is a command published in the GitHub repository UiPath/coder_eval (119 stars, last pushed 3d ago), licensed Apache-2.0. It adds 8 tokens to every session and 14,943 once invoked, about $0.0000 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-30.

Code review Git and workflow Testing agent-evaluation claude claude-code codex coding-agents evaluation-framework

coder-eval-code-review-full

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Context

Scope Selection

What this file has done since we first saw it

Other commands, from other repositories

work

ng-red-team

milestone-status

usage-add

milestone-list

fix