MoAI-ADK is a Go-based harness that organizes and verifies Claude Code work across planning, implementation, synchronization, and review stages. Developers use it to structure agentic coding tasks, apply quality gates, and route work across language models, while the catalogue entries extend its workflow with skills, hooks, commands, MCP servers, instructions, and settings.
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/modu-ai/moai-adk/plangit clone --depth 1 https://github.com/modu-ai/moai-adkWrote 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/modu-ai/moai-adk/plan)<a href="https://agentmods.dev/commands/modu-ai/moai-adk/plan"><img src="https://agentmods.dev/badge/commands/modu-ai/moai-adk/plan.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.00011 | $0.00054 |
| Opus 5 | $0.00005 | $0.00027 |
| Sonnet 5 | $0.00002 | $0.00011 |
| Haiku 4.5 | $0.00001 | $0.00005 |
Grade A, and why
plan 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 5d 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
Use Skill("moai") with arguments: plan $ARGUMENTS
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.
- 5d ago First seen · 8 lines · 11 tokens per session scan A f9afe4ee399c
plan is a command published in the GitHub repository modu-ai/moai-adk (1,197 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 54 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-30.
Other commands, from other repositories
amby.revise
Continue an existing feature's spec (or design) — add and refine in place, with a done-guard.
amby.converge
Check the codebase against spec, plan, and tasks after implementing; append gap tasks, never edit code.
amby.specify
Turn a feature idea into a spec — user stories, EARS requirements, acceptance criteria.
amby.analyze
Cross-check spec, plan, and tasks for coverage, consistency, and dependency-graph health.
amby.design
Design the UI — wireframes, component specs, and design tokens — with a sign-off gate.
amby.implement
Execute the task list, checking off tasks and updating story status as you go.