Borrowing it
Nothing to install: this file belongs to alex-alecu/garden-desk. 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/alex-alecu/garden-desk/main/.claude/commands/garden-desk-code-review.mdgit clone --depth 1 https://github.com/alex-alecu/garden-deskWrote 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/commands/alex-alecu/garden-desk/garden-desk-code-review)<a href="https://agentmods.dev/commands/alex-alecu/garden-desk/garden-desk-code-review"><img src="https://agentmods.dev/badge/commands/alex-alecu/garden-desk/garden-desk-code-review/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/commands/alex-alecu/garden-desk/garden-desk-code-review"><img src="https://agentmods.dev/badge/commands/alex-alecu/garden-desk/garden-desk-code-review.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.00018 | $0.02131 |
| Opus 5 | $0.00009 | $0.01066 |
| Sonnet 5 | $0.00004 | $0.00426 |
| Haiku 4.5 | $0.00002 | $0.00213 |
Grade A, and why
garden-desk-code-review 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 7d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review the given pull request. REVIEW.md at the repository root is the primary review instruction set; CLAUDE.md and the files it imports are secondary general project context.
Agent assumptions (applies to all agents and subagents):
- All tools are functional. Do not test tools or make exploratory calls.
- Only call a tool when required to complete the task.
- Read the pull request only with
gh pr view,gh pr diff, and thegh api .../compareandgh api .../pullsread commands named below; read repository files only withRead,Grep, andGlob. Never rungit. - Models and thinking levels are pinned: the orchestrator runs on the model and effort set by the workflow; subagents are the
review-gate(Haiku, low effort),review-sonnet(Sonnet 5, high effort), andreview-opus(Opus 5, medium effort) agents defined in.claude/agents/. Launch every agent withsubagent_typeset to one of those names and never override its model or effort. Those agents have no Agent tool, so they cannot launch agents of their own.
Waiting for agents (this runs unattended, so it must never stall or loop):
- Agents run in the background. Tell every agent its time budget in its prompt ("You have N seconds; reply with what you have before then"). After launching a group of agents, call
TaskOutputonce per agent withblock: trueand the timeout given for that step. Do not poll, sleep, schedule wakeups, or useMonitor. Only a lens agent that is still running after its first wait gets one moreTaskOutputwith timeout60000; no agent gets a third. - An agent whose final
TaskOutputstatus is notcompleted, or whose output is empty or unusable, has failed: callTaskStopon it and apply the fallback given for that step. - Never end your turn while an agent you launched is still running; every step below ends with all its agents collected or stopped.
Review modes:
- Full review: no earlier claude summary comment exists on the pull request. Review the whole
gh pr diff. - Incremental review: the newest claude summary comment ends with a
Reviewed <sha>line. Review only the commits after that sha, so work is not repeated. PerREVIEW.md, an incremental review posts CRITICAL and WARNING findings only.
Review tiers:
- Small to medium: at most 400 changed lines and at most 15 changed files, after the exclusions in
REVIEW.md. Onereview-opusagent reviews all four lenses and validates its findings. - Large: more than 400 changed lines or more than 15 changed files. Use the full agent set.
- Measure the diff for this run and select the tier one time before a lens agent starts.
Follow these steps precisely:
-
Launch a
review-gateagent that returns: whether the pull request is closed or a draft; the current head sha fromgh pr view <PR> --json headRefOid; and the sha from theReviewed <sha>line of the newest claude comment ingh pr view <PR> --comments, ornone. Wait with timeout45000. Stop if the pull request is closed or a draft. Fallback: continue with a full review. -
Read
REVIEW.mdin full. ReadCLAUDE.mdand any file it references with@syntax. Identify the review lenses thatREVIEW.mddefines under "WHAT TO REVIEW"; each inline[tag]line that introduces a bullet list is one lens. -
Choose the mode. With a reviewed sha, run
gh api repos/<owner>/<repo>/compare/<reviewed-sha>...<head-sha> --jq '{status, files: [.files[] | {filename, additions, deletions, patch}]}'. Ifstatusisaheadandfilesis not empty, the mode is incremental and that output is the diff to review; also collect the earlier claude inline findings withgh api repos/<owner>/<repo>/pulls/<number>/comments --jq '.[] | select(.user.login == "claude[bot]") | {path, line, body}'. Ifstatusisidentical, post nothing and stop. Otherwise (no reviewed sha,behind,diverged, or a failed command) the mode is full.Select the tier after the mode. In full mode, use
gh pr view <PR> --json files --jq '[.files[] | select((.path | test("(^|/)(pnpm-lock.yaml|package-lock.json|yarn.lock)$|(^|/)__snapshots__/")) | not)] | {files: length, lines: (map(.additions + .deletions) | add // 0)}'. In incremental mode, calculate the same counts from the compare outputfilesarray and itsfilename,additions, anddeletionsvalues, with the same path exclusions. Log the counts and the selected tier.
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.
- 7d ago First seen · 59 lines · 18 tokens per session scan A 68531154fb21
garden-desk-code-review is a command published in the GitHub repository alex-alecu/garden-desk (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 18 tokens to every session and 2,131 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
quality-gate
Run the ECC quality pipeline on demand for a file or project scope.
review
Review code changes against project conventions.
review
Review a skill for quality before merge.
review
Review the current diff against project memory.
code-review
Code review a pull request.
review
Perform a comprehensive code review on the following target.