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-cowork --skill moai-reviewgit clone --depth 1 https://github.com/modu-ai/moai-coworkWrote 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-cowork/moai-review)<a href="https://agentmods.dev/skills/modu-ai/moai-cowork/moai-review"><img src="https://agentmods.dev/badge/skills/modu-ai/moai-cowork/moai-review/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-cowork/moai-review"><img src="https://agentmods.dev/badge/skills/modu-ai/moai-cowork/moai-review.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00245 |
| Opus 5.5 | $0.00006 | $0.00098 |
| Sonnet 5.5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
moai-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 10d 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.
This is a copy
100% identical to moai-review — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
이 스킬은 별도 MoAI-ADK의 개발 워크플로우 진입점이다. MoAI-Cowork 실무 플러그인에 포함되는 스킬이 아니다.
- 현재 세션에
moai스킬이 실제 노출되면 해당 정본을 읽고 다음 인수를 전달한다:review $ARGUMENTS. moai스킬이 없으면moai --help로 설치·명령 표면만 확인한다. 이름이 비슷한 Cowork 스킬을 대신 실행하지 않는다.- 실제 제공되는 CLI 동작과 필요한 입력·권한·검증 절차를 확인할 수 있는 범위에서만 진행한다. 확인할 수 없으면 외부 MoAI-ADK 의존성이 없다는 blocker와 필요한 설치 또는 진입 경로를 보고한다.
- 스킬을 읽지 못했거나 업무를 실행하지 않은 상태를 완료로 보고하지 않는다.
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.
- 10d ago Changed · +5 lines 4800cb1dde25
- 21d ago First seen · 8 lines · 14 tokens per session scan A f5536110fd6b
moai-review is a skill published in the GitHub repository modu-ai/moai-cowork (308 stars, last pushed 8d ago), licensed Apache-2.0. It adds 14 tokens to every session and 245 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to moai-review, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
issue-analyzing
Use this skill when the user asks to analyze a specific GitHub issue, understand what area of code an issue affects, assess an issue's scope, or research the code context around an issue — example triggers like "analyze issue.
pr-analyzing
Use this skill when the user asks to analyze a specific GitHub pull request, review a PR's architectural impact, assess what changed in a PR and why it matters, or research the code relationships affected by a PR — example triggers like "analyze PR.
review-pr
Comprehensive PR review -- full branch diff against base, commit-by-commit analysis, breaking change detection, conventional commit verification.
finalize-pr
Automatically finalize pull requests for merge by resolving CodeQL violations, PR feedback, merge conflicts, and CI failures. Handles single PR (current branch or by number), all open PRs in the repo, or all open PRs across the org. Includes bot-authored PRs in all modes.