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.
Borrowing it
Nothing to install: this file belongs to modu-ai/moai-adk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/modu-ai/moai-adk/main/.claude/skills/moai/SKILL.mdgit 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/skills/modu-ai/moai-adk/moai)<a href="https://agentmods.dev/skills/modu-ai/moai-adk/moai"><img src="https://agentmods.dev/badge/skills/modu-ai/moai-adk/moai.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 357 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00059 | $0.07403 |
| Opus 5 | $0.00030 | $0.03701 |
| Sonnet 5 | $0.00012 | $0.01481 |
| Haiku 4.5 | $0.00006 | $0.00740 |
Grade B, and why
moai scanned grade B 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. **Completion condition**: the end state that means "done". Where the condition is machine-verifiable (test exit code, lint-clean state, grep count, bounded turn count), express it in `/moai goal`-compatible form per ` How it starts
The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-execution Context
!git status --porcelain 2>/dev/null || true
!git branch --show-current 2>/dev/null || true
Essential Files
.moai/config/sections/*.yaml
Authority References
Rules and constraints governing all workflows are always loaded from these sources. Do NOT duplicate their content here:
- Core identity, orchestration principles, agent catalog: CLAUDE.md
- Quality gates, security boundaries: .claude/rules/moai/core/moai-constitution.md
- SPEC workflow phases, token budgets: .claude/rules/moai/workflow/spec-workflow.md
- Development methodologies (DDD/TDD): .claude/rules/moai/workflow/spec-workflow.md (Run Phase section)
- Agent definitions: See CLAUDE.md Section 4. For agent creation, use builder-harness subagent (artifact_type=agent).
- @MX tag rules and protocol: .claude/rules/moai/workflow/mx-tag-protocol.md
Routing Observation Ledger
When dispatching a subcommand or workflow, the orchestrator records the routing decision to the append-only routing-ledger (.moai/state/routing-ledger.jsonl) via moai harness ledger record at dispatch time — the request text is piped via stdin and only a privacy-preserving digest is stored, never verbatim user text. As the routed pipeline reaches gate points, machine evidence is appended via moai harness ledger evidence (gate exits, audit verdicts, verify-log paths). Outcome is never supplied as an input; it is finalized from machine evidence only. This observation is opt-in and fail-open — it never blocks routing. NOTE: recording depends on the orchestrator actually invoking moai harness ledger record at dispatch; when the observability opt-in is ON but that record call is not emitted, the ledger stays empty — an un-recorded dispatch, NOT an opt-in-off no-op. Do not read an empty routing-ledger as 'opt-in disabled'.
Intent Router
Raw User Input
$ARGUMENTS
Routing Instructions
[HARD] Route the Raw User Input above using the strict priority order below. Extract the FIRST WORD of the input for subcommand matching. All text after the subcommand keyword is CONTEXT to be passed to the matched workflow — it is NOT a routing signal and MUST NOT influence which workflow is selected.
What ships with it
45 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/anti-patterns.md 11 KB
- references/file-reading-optimization.md 1.9 KB
- references/mx-tag.md 4.3 KB
- references/reference.md 8.5 KB
- workflows/clean.md 13 KB
- workflows/codemaps.md 9.0 KB
- workflows/design.md 8.7 KB
- workflows/e2e.md 25 KB
- workflows/factory.md 11 KB
- workflows/feedback.md 13 KB
- workflows/fix.md 19 KB
- workflows/gate.md 7.8 KB
- workflows/goal.md 11 KB
- workflows/harness-build-entry.md 18 KB
- workflows/harness-builder.md 36 KB
- workflows/harness.md 24 KB
- workflows/loop.md 33 KB
- workflows/moai.md 24 KB
- workflows/mx.md 8.7 KB
- workflows/plan.md 11 KB
- workflows/plan/.gitkeep 0 B
- workflows/plan/clarity-interview.md 12 KB
- workflows/plan/context-discovery.md 3.1 KB
- workflows/plan/spec-assembly.md 31 KB
- workflows/project.md 6.3 KB
- workflows/project/.gitkeep 0 B
- workflows/project/codebase-analysis.md 15 KB
- workflows/project/doc-generation.md 22 KB
- workflows/project/meta-harness.md 9.0 KB
- workflows/project/mode-detection.md 16 KB
- workflows/references/shadcn-component-catalog.md 3.4 KB
- workflows/review.md 37 KB
- workflows/run.md 19 KB
- workflows/run/.gitkeep 0 B
- workflows/run/context-loading.md 11 KB
- workflows/run/mode-orchestration.md 8.3 KB
- workflows/run/phase-execution.md 29 KB
- workflows/run/task-decomposition.md 21 KB
- workflows/sync.md 13 KB
- workflows/sync/.gitkeep 0 B
- workflows/sync/delivery.md 19 KB
- workflows/sync/doc-execution.md 14 KB
- workflows/sync/quality-gates-context.md 9.4 KB
- workflows/sync/quality-gates-quality.md 23 KB
- workflows/todo.md 13 KB
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 · 393 lines · 59 tokens per session scan B 89c81faedacd
moai is a skill published in the GitHub repository modu-ai/moai-adk (1,200 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 7,403 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
github-issue
Creates well-documented GitHub issues (or comments on existing ones) from problems discussed in conversation. Investigates the codebase to map affected layers, files, and data flow, then writes up findings with acceptance criteria — without prescribing fixes. Use when a conversation has identified a problem that needs…
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
cog-meeting-processing
Process meeting recordings and transcripts into decisions, action items, and team dynamics.
cog-team-intelligence
Cross-reference GitHub, Linear, Slack, and PostHog with bidirectional sync for team briefs.
agent-coordination
Coordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
convoy-management
Create, track, and land convoys of related beads as primary work orders in the Gas Town multi-agent orchestration framework.