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-fixgit 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-fix)<a href="https://agentmods.dev/skills/modu-ai/moai-cowork/moai-fix"><img src="https://agentmods.dev/badge/skills/modu-ai/moai-cowork/moai-fix/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-fix"><img src="https://agentmods.dev/badge/skills/modu-ai/moai-cowork/moai-fix.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.00021 | $0.00252 |
| Opus 5.5 | $0.00008 | $0.00101 |
| Sonnet 5.5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
moai-fix 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 9d 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-fix — 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스킬이 실제 노출되면 해당 정본을 읽고 다음 인수를 전달한다:fix $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.
- 9d ago Changed · +5 lines 87420bb98d12
- 20d ago First seen · 8 lines · 21 tokens per session scan A d6ec075cbea1
moai-fix is a skill published in the GitHub repository modu-ai/moai-cowork (308 stars, last pushed 7d ago), licensed Apache-2.0. It adds 21 tokens to every session and 252 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-fix, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
github-actions-silent-failures
Diagnose GitHub Actions workflows that fail silently — a reusable-workflow run with zero jobs/logs, a gh-aw import mis-resolving vs a repo named .github, self-hosted-runner traps. Use when a required check never reds or a run has no jobs.
troubleshoot-worktree
Troubleshoot git worktree, branch, and refname issues.
debug
Analyze errors and apply fixes. Use when you have an error message, traceback, or failing log to diagnose.
debugging
This skill should be used when a test is failing inexplicably, when a runtime error appears in production, when a bug reproduces unpredictably, or when two or more prior fix attempts have failed. Provides a 4-phase systematic debugging workflow — investigate, analyze patterns, form hypothesis, fix with test — to…
debugging
The scientific debugging loop — reproduce first, pull the real event from the repo's observability stack, one hypothesis → one change → one observation, revert failed attempts, escalate instead of thrash. INVOKE PROACTIVELY when diagnosing any bug, error, stack trace, failing or flaky test, crash, regression, or…