Open Code Review is an AI-assisted command-line tool that examines code changes or entire files and produces structured comments tied to specific lines. Developers use it for repository-level reviews, code auditing, and checks such as security, null safety, and thread safety.
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.
git clone --depth 1 https://github.com/alibaba/open-code-reviewWrote 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/alibaba/open-code-review/tag)<a href="https://agentmods.dev/commands/alibaba/open-code-review/tag"><img src="https://agentmods.dev/badge/commands/alibaba/open-code-review/tag/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/alibaba/open-code-review/tag"><img src="https://agentmods.dev/badge/commands/alibaba/open-code-review/tag.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.00000 | $0.00263 |
| Opus 5.5 | $0.00000 | $0.00105 |
| Sonnet 5.5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
tag 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 1mo 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.
What it actually says
/tag
Create an annotated git tag with an auto-generated summary of changes since the last tag.
Arguments
$ARGUMENTS: Optional version number (e.g.,v1.2.0). If omitted, auto-increment the patch version from the latest tag.
Workflow
Step 1: Determine version
- Get the latest tag:
git describe --tags --abbrev=0 - If
$ARGUMENTSis provided and non-empty, use it as the new version. - Otherwise, auto-increment the patch number (e.g.,
v1.1.5→v1.1.6).
Step 2: Generate summary
- Get the commit range: from the latest tag to HEAD.
- Run
git log <latest-tag>..HEAD --onelineto list all commits in this range. - Summarize the changes into a brief tag message (1-3 lines, similar to a commit message style). Focus on what was implemented/fixed, not individual commits.
Step 3: Create tag
Run:
git tag -s <new-version> -m "<summary>"
Report the created tag and its message to the user.
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.
- 1mo ago First seen · 32 lines · 0 tokens per session scan A d66e8833f3a7
tag is a command published in the GitHub repository alibaba/open-code-review (47,499 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 263 tokens. 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
aidd-pr
Review a PR, resolve addressed comments, and generate /aidd-fix delegation prompts for remaining issues.
pre-pr-check
Perform a comprehensive pre-PR check: summarize changes, analyze risk, and generate a review checklist.
create-pr
Create a GitHub pull request from a pushed branch with ticket-aware title and body generation. Not for: committing, pushing, merging, releasing, or editing an existing PR. Output: a dry-run gh pr create command by default, or the created PR URL after explicit execution.
code-review
Code review — local uncommitted changes or GitHub PR (pass PR number/URL for PR mode).
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.
prp-pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.