Uno Platform is an open-source .NET development platform that lets developers build native mobile, web, desktop, and embedded applications from one C# and XAML codebase. It is intended for .NET developers who want to share application code across multiple operating systems and device types. The catalogue entries support development workflows for Uno Platform with skills, agents, commands, and instructions.
Borrowing it
Nothing to install: this file belongs to unoplatform/uno. 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/unoplatform/uno/master/.claude/commands/review-panel.mdgit clone --depth 1 https://github.com/unoplatform/unoWrote 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/unoplatform/uno/review-panel)<a href="https://agentmods.dev/commands/unoplatform/uno/review-panel"><img src="https://agentmods.dev/badge/commands/unoplatform/uno/review-panel.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.00046 | $0.01835 |
| Opus 5 | $0.00023 | $0.00918 |
| Sonnet 5 | $0.00009 | $0.00367 |
| Haiku 4.5 | $0.00005 | $0.00184 |
Grade A, and why
review-panel 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are orchestrating an eight-agent review panel on this repo (the Uno Platform framework). Do not do the review yourself — your job is to pin down the scope, dispatch all eight reviewer subagents in parallel, synthesize their findings into one consolidated report, then capture any lesson the panel learns.
1. Resolve scope
Argument from the user: $ARGUMENTS
- If the argument is non-empty, use it as the scope verbatim. If it looks like a PR reference (
#123,PR 123, a github.com PR URL), resolve the diff viagh pr diff/gh pr view. Otherwise treat it as a git revision range (e.g.HEAD~1,master..HEAD) or a free-form description. - If the argument is empty, auto-resolve in this order:
- Run
git status --porcelain. If there are any staged, unstaged, or untracked changes, the scope is "uncommitted changes (working tree + index + untracked)". - Otherwise run
git rev-parse --abbrev-ref HEAD. If the current branch is not the trunk (masterormain), the scope is "current branch vs trunk". This repo's trunk ismaster; resolve the base withgit merge-base --fork-point master HEADand capture the output as<base>; the scope range is then the explicit<base>..HEAD. If--fork-pointexits with empty stdout (typical after a rebase or across divergent histories), fall back to the literal rangemaster..HEAD.git merge-basereturns a single commit SHA, not a range — never pass it alone togit diff/git log(that would include unrelated ancestor history); always compose the two-dot range form before diffing. - Otherwise stop with a one-line message: "Nothing to review — clean working tree on trunk. Pass a scope argument."
- Run
2. Gather scope detail
Collect — but do not analyze — the concrete change surface so each reviewer sees the same brief:
- File list with stat summary (
git diff --stat <range>orgit status --porcelain+ untracked) - Commit list if a range is in play (
git log --oneline <range>) - Full commit messages if a range is in play (
git log --format="--- commit %H%n%s%n%n%b" <range>) — pass these verbatim toquality,contract, andjeromeso they can evaluate requirement alignment, intentional vs accidental contract changes, and whether the change actually matches its stated intent - Branch name and base
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 · 72 lines · 46 tokens per session scan A 8375d35f695c
review-panel is a command published in the GitHub repository unoplatform/uno (10,038 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 1,835 once invoked, about $0.0002 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.
Other commands, from other repositories
review-feature
Review a KMP feature against architecture patterns and spec.
app-audit
Grade an existing app against the Mobify Studio House KB and Axiom standards — fan out the specialist auditors, produce a severity-ranked gap report, build a remediation backlog, then fix (safe fixes automatically, risky changes only with your approval).
app-review
Run code review on a specific branch or open PR-equivalent.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.
diff-review
Generate a visual diff review for code changes.