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.
npx agentmods add commands/alibaba/open-code-review/taggit clone --depth 1 https://github.com/alibaba/open-code-reviewWhat 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.00000 | $0.00263 |
| Opus 5 | $0.00000 | $0.00131 |
| Sonnet 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 2d 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.
- 2d 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 (21,659 stars, last pushed 4d ago), 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
full-review
Run a full review — code, architecture, browser, and UX. User input: $ARGUMENTS.
commit
Commit current changes. User input: $ARGUMENTS.
harness
Run the full Auto-Harness orchestration flow. /auto-harness:harness.
qa-parallel
Advance parallel Evaluator-side actions only. Auto-selects review, QA, retest, or final report from status.md. /auto-harness:qa-parallel [sprint].
qa
Advance Evaluator-side actions only. Auto-selects review, QA, retest, or final report from status.md. /auto-harness:qa [sprint].
build-parallel
Advance parallel Generator-side actions only. Auto-selects contract, build, or fix from status.md. /auto-harness:build-parallel [sprint].