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 skills add modu-ai/moai-adk --skill hns-oss-docs-readme-syncgit 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/hns-oss-docs-readme-sync)<a href="https://agentmods.dev/skills/modu-ai/moai-adk/hns-oss-docs-readme-sync"><img src="https://agentmods.dev/badge/skills/modu-ai/moai-adk/hns-oss-docs-readme-sync/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/skills/modu-ai/moai-adk/hns-oss-docs-readme-sync"><img src="https://agentmods.dev/badge/skills/modu-ai/moai-adk/hns-oss-docs-readme-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.00971 |
| Opus 5 | $0.00042 | $0.00485 |
| Sonnet 5 | $0.00017 | $0.00194 |
| Haiku 4.5 | $0.00008 | $0.00097 |
Grade A, and why
hns-oss-docs-readme-sync 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README 4-File Sync Procedure
The GitHub-facing README set is 4 files at the repo root:
| File | Locale | Role |
|---|---|---|
README.ko.md |
ko | canonical / primary — author here first |
README.md |
en | derived |
README.ja.md |
ja | derived |
README.zh.md |
zh | derived |
Chain history: the canonical locale was English until 2026-08-17, when card t47 promoted the ko new-skeleton (feature-oriented section structure) to canonical per the operator decision — aligning the README chain with the docs-site chain, which was already ko-canonical. The former en-skeleton redesign reference (
.moai/reports/readme-docs-redesign-20260713.md) is superseded by the ko skeleton and kept as history only.
Procedure
- Author the change in
README.ko.md(Korean) only. Respect the canonical ko section skeleton; keep the file length in the range of the current set. - Derive en, ja, zh — same PR, one derived file per translator worker. Translate the changed sections minimally; do not rewrite untouched prose.
- Preserve verbatim across all 4 files: code blocks, command names, badges, version strings, file paths, tables' structure, Mermaid direction, and the switcher header (below).
- Verify parity (checklist below) before returning.
Language-switcher header contract [HARD]
All 4 files share the same switcher header near the top, linking the sibling files with the label set exactly:
English · 한국어 · 日本語 · 中文
- The current file's own label renders as plain text; the other 3 are links to the sibling README files.
- Never reorder, drop, or re-label the 4 entries.
Section-order parity checklist
-
grep -c '^## ' README.md README.ko.md README.ja.md README.zh.md— identical H2 counts across the 4 files. - H2 section ORDER matches ko (compare
grep '^## 'output order). - H3 counts per section match for sections you touched.
- Table row counts match in touched sections.
- Code-block count matches (
```` grep -c '^```' ````is even and equal). - Switcher header present and correct in all 4.
- URL blacklist clean:
grep -n 'docs\.moai-ai\.dev\|adk\.moai\.com\|adk\.moai\.kr' README*.md→ no matches.
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.
- 12d ago First seen · 89 lines · 83 tokens per session scan A 11ecd2968dc1
hns-oss-docs-readme-sync is a skill published in the GitHub repository modu-ai/moai-adk (1,207 stars, last pushed today), licensed Apache-2.0. It adds 83 tokens to every session and 971 once invoked, about $0.0004 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 skills, from other repositories
code-reviewer
Automatic code quality and best practices analysis. Use proactively when files are modified, saved, or committed. Analyzes code style, patterns, potential bugs, and security basics. Triggers on file changes, git diff, code edits, quality mentions.
test-generator
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.
api-documenter
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.
readme-updater
Keep README files current with project changes. Use when project structure changes, features added, or setup instructions modified. Suggests README updates based on code changes. Triggers on significant project changes, new features, dependency changes.
security-auditor
Continuous security vulnerability scanning for OWASP Top 10, common vulnerabilities, and insecure patterns. Use when reviewing code, before deployments, or on file changes. Scans for SQL injection, XSS, secrets exposure, auth issues. Triggers on file changes, security mentions, deployment prep.
hn-summarize
Fetch and summarize Hacker News / hckrnews.com top stories, articles, and their comment threads. Use when asked to summarize HN front-page stories, a specific HN story plus its discussion, or "the top N from hckrnews".