claw-mo-up

claw-mo-up is a skill for Claude Code, Codex from LeeJuOh/claude-code-zero. It costs 42 tokens per session (1,436 once invoked), scanned A, original, MIT.

A project command that starts or reopens the configured “mo” tool, which displays Markdown documentation in a browser.

In plain words
What is it for?
Use it to preview project documentation, start the viewer for a session, or restart it so new files appear.
Why use it?
It removes the need to remember the startup command and can refresh the viewer when file changes were missed.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the claw-mo plugin — 5 skills, 1 hook shipped together

Install

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.

agentmods
npx agentmods add skills/leejuoh/claude-code-zero/claw-mo-up
Any agent
npx skills add LeeJuOh/claude-code-zero --skill claw-mo-up
Clone the repo
git clone --depth 1 https://github.com/LeeJuOh/claude-code-zero

Made for: Claude Code, Codex.

Or install claw-mo, the plugin that ships this one along with the rest of its 5 skills, 1 hook.

Wrote 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.

agentmods badge for claw-mo-up

README.md
[![agentmods](https://agentmods.dev/badge/skills/leejuoh/claude-code-zero/claw-mo-up.svg)](https://agentmods.dev/skills/leejuoh/claude-code-zero/claw-mo-up)
Your own site
<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>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,436 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash a7a0690caa47, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

plugins/claw-mo/skills/claw-mo-up/SKILL.md · 84 lines

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 — Skip mo --restart when 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-up is only needed to (a) start mo for the first time in a session, (b) recover from a silent fsnotify miss via mo --restart, or (c) reconcile a drifted runtime to saved config. Routine new-file visibility does not require a restart anymore.

  1. Prerequisites: command -v mo >/dev/null 2>&1. If missing, tell user brew install k1LoW/tap/mo and stop.

  2. Project key: git rev-parse --show-toplevel (fallback: $PWD).

  3. Read config from ${CLAUDE_PLUGIN_DATA}/config.json. If no entry for this project, tell the user to run /claw-mo-setup and stop.

  4. v1 migration: If the entry has patterns instead of groups, migrate to groups format and save back.

  5. Probe server: mo --status --json 2>/dev/null. Extract the server whose port matches $PORT.

  6. 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 --reuse flag was passed: skip restart, reuse as-is.

    (c) Server running, live differs from config (treat config as source of truth):

    1. Show a concise diff (groups added/removed, patterns changed) so the user sees why a clear is happening
    2. printf 'y\n' | mo --clear -p $PORT
    3. Start per group as in (a)
    4. Mention that ad-hoc runtime edits were discarded; persist via /claw-mo-manage or /claw-mo-setup next time

Read the full file on GitHub · 84 lines

Changes

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.

  1. 4d ago First seen · 84 lines · 42 tokens per session scan A a7a0690caa47

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

mcporter

List, auth, and call MCP servers/tools from the terminal.

NousResearch/hermes-agent · 16 tokens

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.

affaan-m/ECC · 57 tokens

sector-rotation

行业轮动分析——申万行业景气度评分、行业动量排名、产业链传导、估值/盈利/资金流多维比较框架.

HKUDS/Vibe-Trading · 39 tokens

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.…

mem0ai/mem0 · 273 tokens

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.

pydantic/pydantic-ai · 55 tokens

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…

omnigent-ai/omnigent · 84 tokens