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 receptron/mulmoclaude --skill mc-zenngit clone --depth 1 https://github.com/receptron/mulmoclaudeWrote 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/receptron/mulmoclaude/mc-zenn)<a href="https://agentmods.dev/skills/receptron/mulmoclaude/mc-zenn"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-zenn/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/receptron/mulmoclaude/mc-zenn"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-zenn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
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 →
- medium MCP Rug Pull · line 51 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 56 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 58 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 90 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 144 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]
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.00137 | $0.02117 |
| Opus 5.5 | $0.00055 | $0.00847 |
| Sonnet 5.5 | $0.00027 | $0.00423 |
| Haiku 4.5 | $0.00014 | $0.00212 |
Grade A, and why
mc-zenn 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 1mo 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zenn
A bundled MulmoClaude preset skill (mc- prefix = launcher-managed; do not edit
this file in the workspace, it is overwritten on every server boot).
Help the user share what they did in MulmoClaude as a Zenn tech article. Two jobs in one skill: (1) make sure a Zenn project exists in the workspace and (2) write an article from the work. Writing auto-runs setup first when the project isn't there yet, so the user can jump straight to "Zenn にまとめて" without thinking about setup.
Keep the machinery invisible — the user shouldn't have to think about slugs, frontmatter, or zenn-cli internals.
Where things live
The Zenn project is a git repo inside the workspace at github/zenn/
(cwd-relative — the agent runs with cwd = workspace, so every path here is plain
cwd-relative). Articles are markdown files at github/zenn/articles/<slug>.md.
Zenn publishes by syncing a connected GitHub repo, so this directory is a real
git repo the user pushes to.
Is it initialized? The project is ready when github/zenn/articles/ exists.
Use that as the idempotency marker — never re-init a directory that already has
it.
Workflow 1: set up the Zenn project (idempotent)
Triggers: "Zenn のリポを用意して", "Zenn 始めたい", "set up Zenn", "まだ Zenn 作ってない". Also runs automatically as Step 0 of Workflow 2.
Step 1 — check first. If github/zenn/articles/ already exists, the project
is ready: say so in one line and stop. Re-initializing is never correct. Only
continue when it's missing.
Step 2 — clone or init. Ask which with one presentForm (two choices),
unless the user already told you:
-
Clone an existing Zenn repo (they already write Zenn on GitHub). Get the repo URL, then:
git clone <url> github/zennnpx zennfetches zenn-cli on demand, so a missing local dependency is fine. -
Create a fresh project (standard zenn-cli flow):
mkdir -p github/zenn cd github/zenn && npm init --yes && npm install zenn-cli && npx zenn init(
yarn add zenn-cliworks too if the user prefers yarn.)npx zenn initscaffoldsarticles/,books/, and a README. Then make it a git repo:cd github/zenn && git init -b main
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.
- 1mo ago First seen · 168 lines · 137 tokens per session scan A d16e828ee25f
mc-zenn is a skill published in the GitHub repository receptron/mulmoclaude (386 stars, last pushed yesterday), licensed MIT. It adds 137 tokens to every session and 2,117 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
ai-skill
A Chinese-language skill discovery and management system for finding, evaluating, installing, recommending, browsing, updating, or removing agent skills and extensions.
add-resend
Add Resend (email) channel integration via Chat SDK.
add-macos-statusbar
Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.
excel-conditional-filtering-optimization
A workflow for filtering Excel spreadsheet rows using several numeric conditions and exporting the matching results. Excel is a spreadsheet format that can contain multiple worksheets and large tables.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
text-normalization-and-large-file-processing
Instructions for cleaning spreadsheet text and number columns, including removing stray prefixes from numbers and keeping only Chinese characters in selected text.