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-manage-skillsgit 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-manage-skills)<a href="https://agentmods.dev/skills/receptron/mulmoclaude/mc-manage-skills"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-manage-skills/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-manage-skills"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-manage-skills.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00101 | $0.01560 |
| Opus 5 | $0.00051 | $0.00780 |
| Sonnet 5 | $0.00020 | $0.00312 |
| Haiku 4.5 | $0.00010 | $0.00156 |
Grade D, and why
mc-manage-skills scanned grade D 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Friendly, practical. Don't lecture about staging files, paths, or hooks — Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
(the bridge hook only mirrors deletes that match this shape; bulk `rm -rf` of How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill manager
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 manage project-scope Claude Code skills. The skill body
that Claude Code reads lives at .claude/skills/<slug>/SKILL.md, but agents
must not write there directly — Claude Code's permission system treats
.claude/ as a self-modification surface and the host GUI cannot answer the
resulting prompt, so the write hangs.
Instead, edit the staging file at data/skills/<slug>/SKILL.md. A PostToolUse
hook mirrors every Write / Edit / rm on those staging files into
.claude/skills/<slug>/SKILL.md (or removes the entire dir on delete) and
then asks the server to re-register skills — no restart needed. The user
never sees the staging vs. canonical split; they just say "skill 化して".
The user-scope folder ~/.claude/skills/ is read-only territory managed
outside MulmoClaude — don't touch those.
End with a one-line confirmation ("Saved as foo-skill." / "Removed foo-skill.") so the user can verify without scrolling.
Collections (a skill + a schema.json)
If the user wants a small data app — a list/table they can view and edit
(a swimming log, a recipe box, a client database) — that's a collection
skill: a skill dir that also ships a schema.json (and optional
templates/*.md). Author all of them under the same staging dir
(data/skills/<slug>/SKILL.md + data/skills/<slug>/schema.json +
data/skills/<slug>/templates/*.md); the same bridge hook mirrors those three
file kinds into .claude/skills/<slug>/ and the collection appears at
/collections/<slug>. Read config/helps/collection-skills.md first — it
is the authority on the schema DSL (field types, relations, derived fields,
actions). Don't hand-roll a schema from memory.
Workflow 1: save a new skill
Triggers: "skill 化して", "save this as a skill", "make this reusable", "そのまま skill に".
Step 1 — distil. If the user is asking you to skill-ify the current
conversation, read the chat transcript first. The transcript lives at
chat/<session-id>.jsonl; if you don't know the session id, list the
directory and pick the most-recent one. Reduce the conversation into a
focused markdown body in second person ("First, do X. Then, do Y.") that
captures the reusable workflow — not the one-off details that won't generalise.
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 · 142 lines · 101 tokens per session scan D b4f3c6de6862
mc-manage-skills is a skill published in the GitHub repository receptron/mulmoclaude (347 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 1,560 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it D with 2 findings (strips warnings and disclaimers, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…