What is publish-mulmoclaude?

A release procedure for publishing the mulmoclaude package to npm, the JavaScript package registry. It checks dependencies, workspace package versions, builds, and the package archive before publishing.

Use it to audit dependencies, detect workspace drift, build the app and packages, test the npm tarball, and publish dependent packages when needed.

It catches missing imports, outdated local package versions, and incomplete build output that could make the published package fail.

How receptron/mulmoclaude configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to receptron/mulmoclaude. 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/receptron/mulmoclaude/main/.claude/skills/publish-mulmoclaude/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/receptron/mulmoclaude

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/receptron/mulmoclaude/publish-mulmoclaude/github.svg)](https://agentmods.dev/skills/receptron/mulmoclaude/publish-mulmoclaude)

Your own site

<a href="https://agentmods.dev/skills/receptron/mulmoclaude/publish-mulmoclaude"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/publish-mulmoclaude/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/receptron/mulmoclaude/publish-mulmoclaude"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/publish-mulmoclaude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,458 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 9 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Tool Misuse · line 125
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
high Tool Misuse · line 164
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
high Tool Misuse · line 125
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
high Tool Misuse · line 164
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
medium MCP Rug Pull · line 91
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]
medium MCP Rug Pull · line 173
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]
medium MCP Rug Pull · line 245
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]
medium MCP Rug Pull · line 160
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]
medium Rogue Agent · line 279
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00036	$0.05458
Opus 5	$0.00018	$0.02729
Sonnet 5	$0.00007	$0.01092
Haiku 4.5	$0.00004	$0.00546

Measured 13d ago against content hash bd66dd251ccd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade B, and why

publish-mulmoclaude scanned grade B with 2 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 13d 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.

Recursive force deletemediumDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf /tmp/mc-test && mkdir /tmp/mc-test && cd /tmp/mc-test

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

( while ! curl -s -o /dev/null -w "%{http_code}" http://127.0.0.1:3097/ 2>/dev/null | grep -q 200; do sleep 1; done; echo OK )

.claude/skills/publish-mulmoclaude/SKILL.md · 309 lines

How it starts

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

Publish MulmoClaude

mulmoclaude is a launcher that bundles the whole app into one npm package. Unlike /publish (which handles a single self-contained package), this flow has three traps that bit us on 0.1.0:

The package's dependencies must cover every import "…" in server/ — the root package.json isn't shipped, so implicit inheritance doesn't exist.
@mulmobridge/* workspace packages can drift — local src/ adds exports without a version bump, so npm install resolves to an older published dist/ that's missing them. All dependents fail at runtime.
prepare-dist.js runs via prepack, so both npm pack and npm publish invoke it — but you still need yarn build first (for dist/client/) and yarn build:packages if any workspace package was bumped. (Earlier versions used prepublishOnly, which npm 10+ no longer fires on npm pack, so the §4 tarball test silently shipped a 4-file stub.)

CI coverage — the first-line defence

As of PR #669 / #688, all three traps run automatically on every PR that touches the launcher via .github/workflows/mulmoclaude_smoke.yaml, driven by scripts/mulmoclaude/smoke.mjs:

§1 deps audit → scripts/mulmoclaude/deps.mjs — bare imports + dynamic import("pkg") in server/*.ts checked against packages/mulmoclaude/package.json (including optionalDependencies / peerDependencies).
§2 workspace drift → scripts/mulmoclaude/drift.mjs — local src/index.ts value-export lines compared against the registry-published dist (fetched from registry.npmjs.org + unpkg), not node_modules — the workspace symlink would otherwise always match.
§4 tarball boot → scripts/mulmoclaude/tarball.mjs — npm pack + clean install + launcher start with DISABLE_SANDBOX=1 and a stubbed claude CLI + HTTP 200 on /.

Before releasing, the go/no-go is: "latest MulmoClaude publish smoke run on main is green." Run the manual steps below only if you need to cover a scenario CI doesn't (e.g. the --force publish path, or publishing a cascaded @mulmobridge/* dep).

Read the full file on GitHub · 309 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.

13d ago First seen · 309 lines · 36 tokens per session scan B bd66dd251ccd

Subscribe to this mod's changes

publish-mulmoclaude is a skill published in the GitHub repository receptron/mulmoclaude (347 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 5,458 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens