MoonMcp: Skill for Claude Code

.claude/skills/run-coordination/SKILL.md

run-coordination is a skill for Claude Code, Codex from Moonwuk/MoonMcp. It costs 47 tokens per session (835 once invoked), scanned A, original, MIT.

A coordinator for assessment runs made up of multiple tasks, specialist roles, dependencies, budgets, and shared evidence. It keeps persistent run state so work can be resumed without relying on chat history.

In plain words
What is it for?
Use it to resume a run, inspect status, select the next unblocked task, delegate independent work, and finish an assessment while preserving its artifacts.
Why use it?
It reduces duplicated work and unsafe parallel changes by showing what is unfinished, blocked, or already complete. It also keeps task boundaries, evidence, budgets, and stopping conditions visible.

Skill for Claude CodeCodex

Written for Claude Code and Codex: installed under .claude/, but also agents/openai.yaml present.

This is Moonwuk/MoonMcp's own configuration. It tells Claude Code and Codex how to work on MoonMcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything MoonMcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Moonwuk/MoonMcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Moonwuk/MoonMcp/main/.claude/skills/run-coordination/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Moonwuk/MoonMcp

Made for: Claude Code, Codex.

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 run-coordination

README.md
[![agentmods](https://agentmods.dev/badge/skills/moonwuk/moonmcp/run-coordination/github.svg)](https://agentmods.dev/skills/moonwuk/moonmcp/run-coordination)
Your own site
<a href="https://agentmods.dev/skills/moonwuk/moonmcp/run-coordination"><img src="https://agentmods.dev/badge/skills/moonwuk/moonmcp/run-coordination/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.

agentmods 80×15 button for run-coordination

Your own site · 80×15
<a href="https://agentmods.dev/skills/moonwuk/moonmcp/run-coordination"><img src="https://agentmods.dev/badge/skills/moonwuk/moonmcp/run-coordination.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 835 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00047 $0.00835
Opus 5.5 $0.00019 $0.00334
Sonnet 5.5 $0.00009 $0.00167
Haiku 4.5 $0.00005 $0.00084

Measured 14d ago against content hash 12d3b3da6723, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

run-coordination 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 14d 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.

.claude/skills/run-coordination/SKILL.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run Coordination

Drive assessment work through persistent state rather than chat memory. Keep the coordinator responsible for task boundaries, policy, evidence integration, and stopping conditions—not for doing every specialist task itself.

Adapted for security runs from obra/superpowers' MIT-licensed executing-plans, dispatching-parallel-agents, and finishing-a-development-branch workflows.

Resume before acting

  1. Call run_status(run_id, include_events=true).
  2. Recall memory_brief(target) and inspect runs://recent when the run ID is unknown.
  3. Verify the run is running, scope/program identity is still correct, and budgets remain.
  4. Inspect unfinished tasks, dependencies, coverage, and recent artifacts.
  5. Do not repeat completed work unless the evidence is stale or invalid.

Dispatch safely

Use run_next for the highest-priority unblocked task. Delegate only tasks that are independent in target state and do not mutate the same session or workflow.

Each worker receives:

  • run ID and task ID;
  • exact target and scope constraints;
  • role and falsifiable objective;
  • relevant curated memory and untrusted evidence references;
  • permitted risk tier and remaining budget;
  • required output/evidence format;
  • explicit stop conditions.

Parallelize passive research or independent hosts. Serialize authentication flows, shared-account mutations, rate-limit tests, purchases, password resets, races, and any task whose result changes another task's baseline.

Task lifecycle

  1. Set the selected task to running with run_task_update.
  2. Execute only its bounded objective.
  3. Store material evidence with run_artifact_add.
  4. Update relevant coverage with the evidence reference.
  5. Consume measured usage through run_usage.
  6. Set the task to completed, blocked, failed, or cancelled; include a concise result.
  7. Create follow-up tasks only when new evidence justifies them. Deduplicate against existing tasks and memory.

Never mark a task complete merely because a tool returned successfully. Completion means its hypothesis or deliverable was resolved.

Read the full file on GitHub · 83 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 14d ago First seen · 83 lines · 47 tokens per session scan A 12d3b3da6723

Subscribe to this mod's changes

run-coordination is a skill published in the GitHub repository Moonwuk/MoonMcp (0 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 835 once invoked, about $0.0002 per session on Opus 5.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-10-13.