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/ambystechcom/ambykit/amby.reviewgit clone --depth 1 https://github.com/ambystechcom/AmbyKitWrote 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/ambystechcom/ambykit/amby.review)<a href="https://agentmods.dev/commands/ambystechcom/ambykit/amby.review"><img src="https://agentmods.dev/badge/commands/ambystechcom/ambykit/amby.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.00017 | $0.00371 |
| Opus 5 | $0.00009 | $0.00186 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
amby.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 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.
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
Review $ARGUMENTS (an artifact path, e.g. specs/NNN-slug/spec.md) as a different role.
If the path does not exist, stop and name the phase that produces it.
- Pick the reviewer:
--as <id>→@.amby/roles/<id>.md; otherwise QA for a spec or tasks, Architect for a plan, PM for a UI design. If the file is missing, stop and list.amby/roles/. Say which role you are acting as in your first line. - Read only the artifact (and its spec, if reviewing a plan or tasks). Apply the role's focus
checklist. Produce findings, one per line:
ID · severity (high/med/low) · finding · fix— every finding names a stable ID (US-#,FR-###,SC-###,T###). Modify nothing. - Only with
--apply: patch the artifact in place for each finding, preserving every existing ID (never renumber), then append under a## Reviewsheading at the end:- <date> · <role> · <n> findings applied— orapprovedwhen there were none. - This is advisory: no phase waits on a review. End with the findings count and the next phase to run.
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 · 21 lines · 17 tokens per session scan A 513042e5e123
amby.review is a command published in the GitHub repository ambystechcom/AmbyKit (2 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 371 once invoked, about $0.0001 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-31.
Other commands, from other repositories
oss-docs
(user-owned) oss-docs harness — README 4-locale + docs-site publishing for the moai-adk-go OSS project (adk.mo.ai.kr, Vercel auto-deploy).
release-update
(dev-only) release-update maintainer harness — Claude Code upstream change tracker (release-notes version-delta sweep + docs sync). NOT distributed to user projects.
github
(dev-only) github maintainer harness — GitHub issue-fix and PR-review via gh CLI. NOT distributed to user projects.
release
(dev-only) release maintainer harness — MoAI-ADK production release (Enhanced GitHub Flow, scripts/release.sh + GoReleaser). NOT distributed to user projects.
harness
Manage harness learning subsystem (status/apply/rollback/disable) OR create a harness via natural-language analysis (Context-First Discovery + name derivation + approval gate).
e2e
Create and run E2E tests across web, mobile, and desktop with auto-detection and CLI-first toolchains.