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-e2egit 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-e2e)<a href="https://agentmods.dev/skills/modu-ai/moai-cowork/moai-e2e"><img src="https://agentmods.dev/badge/skills/modu-ai/moai-cowork/moai-e2e/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-e2e"><img src="https://agentmods.dev/badge/skills/modu-ai/moai-cowork/moai-e2e.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.00029 | $0.00262 |
| Opus 5.5 | $0.00012 | $0.00105 |
| Sonnet 5.5 | $0.00006 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
moai-e2e 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-e2e — 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스킬이 실제 노출되면 해당 정본을 읽고 다음 인수를 전달한다:e2e $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 22fcbf304108
- 21d ago First seen · 8 lines · 29 tokens per session scan A c78552ed396b
moai-e2e is a skill published in the GitHub repository modu-ai/moai-cowork (308 stars, last pushed 7d ago), licensed Apache-2.0. It adds 29 tokens to every session and 262 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-e2e, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
k8s-sidecar-testing
Test the nat464-sidecar demo topology in a selected Kubernetes test namespace, verify IPv6 translation paths, and compare HTTP latency. Includes optional disposable Multipass/k3s setup.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
playwright-cursor-rules
Expert guidance for Playwright end-to-end testing with TypeScript and JavaScript best practices.
qa-testing-strategy
Designs risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, choosing test layers, or establishing release criteria.
qa-persona-testing
Tests apps as an ICP persona through browser automation and reports friction, fixes, and risks. Use when running persona-based, ICP, or synthetic-user testing.