agentmods.dev

coder-eval-code-review-full

coder-eval-code-review-full is a command for Claude Code from UiPath/coder_eval. It costs 8 tokens per session (14,940 once invoked), scanned A, original, Apache-2.0.

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.

In plain words
What is it for?
Use it to review all code, uncommitted or staged work, branch differences, unpushed commits, or a specific GitHub pull request.
Why use it?
It gives developers a defined review scope and a repeatable way to inspect code quality before merging or releasing changes.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is | ... | ../10 | .. | .. | .. | .. | ... |.

not rated 151repo changed 29d ago A scan 8 tokens original Apache-2.0

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

Compare 6 commands from other repositories ↓
View source ↗ UiPath/coder_eval coder-eval.com
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/UiPath/coder_eval
agentmods
npx agentmods add commands/uipath/coder_eval/coder-eval-code-review-full

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.

agentmods badge for coder-eval-code-review-full

README.md
[![agentmods](https://agentmods.dev/badge/commands/uipath/coder_eval/coder-eval-code-review-full/github.svg)](https://agentmods.dev/commands/uipath/coder_eval/coder-eval-code-review-full)
Your own site
<a href="https://agentmods.dev/commands/uipath/coder_eval/coder-eval-code-review-full"><img src="https://agentmods.dev/badge/commands/uipath/coder_eval/coder-eval-code-review-full/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.

agentmods 80×15 button for coder-eval-code-review-full

Your own site · 80×15
<a href="https://agentmods.dev/commands/uipath/coder_eval/coder-eval-code-review-full"><img src="https://agentmods.dev/badge/commands/uipath/coder_eval/coder-eval-code-review-full.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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,940 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.14940
Opus 5.5 $0.00003 $0.05976
Sonnet 5.5 $0.00002 $0.02988
Haiku 4.5 $0.00001 $0.01494

Measured 29d ago against content hash 50e824be2554, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 29d 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.

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

  1. 29d ago Changed 50e824be2554
  2. 1mo ago 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 (151 stars, last pushed today), licensed Apache-2.0. It adds 8 tokens to every session and 14,940 once invoked, about $0.0000 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.

Claude CodeCode reviewagent-evaluationclaudecodexcoding-agentsevaluation-framework
Related

Other commands, from other repositories

review-pr

Command "review-pr" from saski/arnesto, covering review pr, what this command does, workflow steps, phase 0: initialize review and phase 1: analysis & summary.

saski/arnesto · 0 tokens

review_prs

Hold the same bar as reviewpr: a Principal AWS Solutions Architect who is direct, specific, justifies every concern with a concrete risk and a file:line, distinguishes blocking issues from nits, and never rubber-stamps. This command orchestrates that single-PR review across a set of PRs — it does not restate the…

aws-samples/sample-autonomous-cloud-coding-agents · 0 tokens

review_pr

Review as a Principal AWS Solutions Architect. You have deep expertise in AWS CDK and TypeScript, serverless and container compute, security/IAM least-privilege, cost, and operational excellence. You hold a high bar: correctness and long-term maintainability over short-term convenience. You are direct, specific, and…

aws-samples/sample-autonomous-cloud-coding-agents · 0 tokens

harness-review

Review the current change set from an opposing harness-engineering perspective.

harnessworks/harness-starter-kit · 0 tokens

prepare-review

Package codebase for external review using RepoMix.

stefan-jansen/claude-code-toolkit · 0 tokens

run-technical-review

Run /run-technical-review as a BACKGROUND task so this chat stays responsive. If the runinbackground tool is available: call runinbackground with name "Technical review + fix", completionmode "presentresult", the review instruction below, and a messagesequence with one follow-up message (id "fix") carrying the fix…

manishiitg/coding-agent-loop · 0 tokens