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 skills/leejuoh/claude-code-zero/claw-mo-upnpx skills add LeeJuOh/claude-code-zero --skill claw-mo-upgit clone --depth 1 https://github.com/LeeJuOh/claude-code-zeroWrote 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/leejuoh/claude-code-zero/claw-mo-up)<a href="https://agentmods.dev/skills/leejuoh/claude-code-zero/claw-mo-up"><img src="https://agentmods.dev/badge/skills/leejuoh/claude-code-zero/claw-mo-up.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.00042 | $0.01436 |
| Opus 5 | $0.00021 | $0.00718 |
| Sonnet 5 | $0.00008 | $0.00287 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
claw-mo-up 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claw-mo-up
Bring up the mo markdown viewer for the current project and open the browser. When a server is already running, restart it by default so new files on disk become visible (fsnotify can silently miss events).
For config schema, decision tree, --restart vs --clear semantics, and browser opening: read ${CLAUDE_PLUGIN_ROOT}/references/shared.md
Arguments
$ARGUMENTS(optional)--reuse— Skipmo --restartwhen live matches config. Use this when the running session is known-good and the user explicitly wants zero interruption.
Steps
[!NOTE] With autosync enabled (default),
/claw-mo-upis only needed to (a) start mo for the first time in a session, (b) recover from a silent fsnotify miss viamo --restart, or (c) reconcile a drifted runtime to saved config. Routine new-file visibility does not require a restart anymore.
-
Prerequisites:
command -v mo >/dev/null 2>&1. If missing, tell userbrew install k1LoW/tap/moand stop. -
Project key:
git rev-parse --show-toplevel(fallback:$PWD). -
Read config from
${CLAUDE_PLUGIN_DATA}/config.json. If no entry for this project, tell the user to run/claw-mo-setupand stop. -
v1 migration: If the entry has
patternsinstead ofgroups, migrate togroupsformat and save back. -
Probe server:
mo --status --json 2>/dev/null. Extract the server whose port matches$PORT. -
Branch on state — see the decision tree in
shared.md:(a) No server on this port → start per group sequentially:
mo --no-open -w 'pattern1' -w 'pattern2' --target groupName -p $PORT mo --no-open -w 'pattern3' --target anotherGroup -p $PORT(b) Server running, live matches config:
- Default:
mo --restart -p $PORT— fresh fsnotify scan, session preserved. This is the main fix for the "docs exist on disk but don't show up in mo" class of bug. - If
--reuseflag was passed: skip restart, reuse as-is.
(c) Server running, live differs from config (treat config as source of truth):
- Show a concise diff (groups added/removed, patterns changed) so the user sees why a clear is happening
printf 'y\n' | mo --clear -p $PORT- Start per group as in (a)
- Mention that ad-hoc runtime edits were discarded; persist via
/claw-mo-manageor/claw-mo-setupnext time
- Default:
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.
- 4d ago First seen · 84 lines · 42 tokens per session scan A a7a0690caa47
claw-mo-up is a skill published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 5d ago), licensed MIT. It adds 42 tokens to every session and 1,436 once invoked, about $0.0002 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
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
sector-rotation
行业轮动分析——申万行业景气度评分、行业动量排名、产业链传导、估值/盈利/资金流多维比较框架.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…