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/kaeawc/auto-mobile/auto-mobile-code-reviewgit clone --depth 1 https://github.com/kaeawc/auto-mobileWrote 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/kaeawc/auto-mobile/auto-mobile-code-review)<a href="https://agentmods.dev/commands/kaeawc/auto-mobile/auto-mobile-code-review"><img src="https://agentmods.dev/badge/commands/kaeawc/auto-mobile/auto-mobile-code-review.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 | $0.00063 | $0.07309 |
| Opus 5 | $0.00032 | $0.03655 |
| Sonnet 5 | $0.00013 | $0.01462 |
| Haiku 4.5 | $0.00006 | $0.00731 |
Grade A, and why
auto-mobile-code-review scanned grade A with 1 finding 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
array/argv form, multiline argv, `exec`/`execSync`, `spawnSync`, destructured How it starts
The opening of the file, as written. The whole thing — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AutoMobile Code Review
Review a change — a PR ($ARGUMENTS = its number) or, with no argument, the current branch's
diff vs origin/main. Few verified findings beat many plausible ones.
Never post to GitHub. No review comments, reviews, or summaries. Report findings in the session. The only permitted GitHub write is resolving a review thread, under the conditions in Working our own PR.
Review against the author's intent and the issue the change serves, not the diff in isolation. Ask rather than assert when genuinely unsure — sometimes you missed something. Name what's genuinely good in a sentence; never manufacture it.
Step 0 — Resolve the diff base
Everything below reuses $BASE, so establish it first. Which base is correct depends on the
mode, and getting it wrong silently scopes the review to the wrong commits:
git fetch origin main
# PR mode — the local checkout is usually NOT the PR branch, so HEAD is unrelated to it.
# The leading + forces the update: without it, re-fetching after a force-push is rejected
# non-fast-forward and Step 0 fails before refreshing anything.
git fetch origin "+pull/<PR>/head:refs/remotes/pr/<PR>"
BASE=$(git merge-base "refs/remotes/pr/<PR>" origin/main)
DIFF_ARGS=("$BASE" "refs/remotes/pr/<PR>") # two endpoints: the PR head, not your tree
# Branch mode — one endpoint, so the diff includes uncommitted work. Naming HEAD as a
# second endpoint would silently drop every working-tree edit.
BASE=$(git merge-base HEAD origin/main)
DIFF_ARGS=("$BASE")
Use "${DIFF_ARGS[@]}" for every diff below. The distinction is not cosmetic: in branch mode a
two-endpoint diff omits exactly the uncommitted changes the review is supposed to cover.
Both obvious branch-mode alternatives are wrong in a common case: origin/main...HEAD (three
dots) is committed work only and reports zero files against a dirty tree, silently scoping
the review to nothing; git diff origin/main (no dots) picks up uncommitted work but, when the
branch is behind main, folds main's newer commits in as reverse-diffs.
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.
- 4d ago First seen · 463 lines · 63 tokens per session scan A a67433b43036
auto-mobile-code-review is a command published in the GitHub repository kaeawc/auto-mobile (45 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 7,309 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
build-verify
Run the full build / test / analyze / format verification pass for this Flutter app.
create-pr-from-staged-changes
You are helping to create a pull request following the iOS team's standard template.
apollo-status
Show the current Apollo removal migration progress.
ios-privacy
Prepare privacy labels, permissions, policy links, and data-use truth for iOS release.
initialize-ios
Manual override: initialize ast-index for iOS/Swift/ObjC project.