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 instructions/modu-ai/moai-adk/agents-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/instructions/modu-ai/moai-adk/agents-md)<a href="https://agentmods.dev/instructions/modu-ai/moai-adk/agents-md"><img src="https://agentmods.dev/badge/instructions/modu-ai/moai-adk/agents-md.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.03222 | $0.03222 |
| Opus 5 | $0.01611 | $0.01611 |
| Sonnet 5 | $0.00644 | $0.00644 |
| Haiku 4.5 | $0.00322 | $0.00322 |
Grade A, and why
moai-adk AGENTS.md 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- moai-cowork AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — standing contract for agents in this repository
Every clause here binds a turn regardless of which agent harness drives it. The file is
self-sufficient: it assumes no other instruction file is loaded, and no nested AGENTS.md
exists anywhere in this repository.
Budget warning. A personal ~/.codex/AGENTS.md joins the same merged chain and is consumed
before this file, narrowing what the project's contract can carry. Overflow is dropped from the
tail, silently — no warning, no stderr, exit 0. Clauses below are ordered most-critical-first
for that reason.
Obligations are carried from .claude/rules/moai/** and CLAUDE.md, which remain the source of
truth; compression removed rationale and incident records, never an obligation. Claude-only
mechanisms (the question channel, subagent spawning, skills, session handoff) stay there.
1. Evidence and verification claims
No unobserved claim. An actor MUST NOT assert a verification, a completion, a defect / debt / drift, OR the premise underlying a recommendation it did not actually verify with the domain's mechanical tooling. Evidence absent is not evidence of success — nor of failure. The absence of a failure signal never establishes that a check passed; a text-pattern inference is a hypothesis, not a verified defect; a reference existing does not establish that the referenced capability is still live. Reachability is not justification.
Baseline-integrity attribution. Every verification claim MUST be attributed to an actually-measured baseline — the command that was run plus the output observed, in this run, against this tree. A figure carried over from another package, tree, or point in time is not a baseline; using it as a fresh measurement violates this. Anything unattributed is a Gap, not a Claim.
Evidence-bearing report format. Verification and completion reports SHOULD carry five sections, on every report and not only the first: Claim (what is asserted); Evidence (the command run plus its verbatim output — a summary is not evidence); Baseline-attribution (what it was measured against, in this run); Gaps (what was explicitly NOT observed — an empty Gaps section asserts nothing was left unobserved, which must itself be true); Residual-risk (what could still be wrong despite what was observed).
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.
- yesterday First seen · 243 lines · 3,222 tokens per session scan A eda0882052e3
moai-adk AGENTS.md is an instructions file published in the GitHub repository modu-ai/moai-adk (1,200 stars, last pushed 2d ago), licensed Apache-2.0. It adds 3,222 tokens to every session, about $0.0161 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-09-03.
Other instructions, from other repositories
claude-code-hooks CLAUDE.md
Instructions for shanraisshan/claude-code-hooks, covering claude code hooks, project structure, critical: hook count consistency, agent hooks and workflows.
shanraisshan CLAUDE.md
Claude Code instructions for shanraisshan/shanraisshan, covering claude.md, what this repo is, key files, badge formatting rules and reddit views (badges at >= 50k).
agentfactory CLAUDE.md
Claude Code instructions for stempeck/agentfactory, covering agentfactory, build commands, dependencies, project structure and cli commands.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).