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/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/app-review)<a href="https://agentmods.dev/commands/vmobifystudio/app-dev-team/app-review"><img src="https://agentmods.dev/badge/commands/vmobifystudio/app-dev-team/app-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/vmobifystudio/app-dev-team/app-review"><img src="https://agentmods.dev/badge/commands/vmobifystudio/app-dev-team/app-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.00012 | $0.00157 |
| Opus 5.5 | $0.00005 | $0.00063 |
| Sonnet 5.5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
app-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 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
/app-review — Review a branch
Target: $ARGUMENTS
Steps
-
Resolve
$ARGUMENTSto a branch name. If it looks like a ticket ID (APP-NNN), look up the matching branch indocs/31-board.md. -
Spawn the
code-revieweragent with the branch name and ticket ID. -
Print the verdict verbatim. If
REQUEST CHANGES, also print suggested next step (re-spawn the developer, or ask user how to proceed).
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 · 18 lines · 12 tokens per session scan A 4051b49d158c
app-review is a command published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 157 once invoked, about $0.0000 per session on Opus 5.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-31.
Other commands, from other repositories
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
loop-task
Run a task through a maker/checker loop until done (triage → implement → verify → gate).
cost-estimate
Estimate a target's tokens, agent-compute time, and (when grounded) cost before it runs — the prospective sibling of /cost-capture. Dispatches the read-only cost-estimator agent, validates the returned record, and writes it after you dispose.
harness-sync
Detect drift across all push-direction control surfaces, present the full picture, and apply the user's selected fixes via the existing primitives — single human-instigated entry point for keeping convention files in sync with HARNESS.md. ONBOARDING.md staleness is surfaced but not auto-fixed; users run…
harness-affordance
Manage the project's affordance inventory — declared tools the agent can invoke, the identity each tool runs under, and the audit trail each tool produces. Subcommands - discover (scan config to produce a draft inventory), add (promote a draft into HARNESS.md with governance metadata), review (re-validate one…
cost-capture
Capture AI tool cost data — guide through provider dashboards, record spend and token usage, compare to previous snapshot, update MODELROUTING.md.