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-wiki-health-checkgit 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-wiki-health-check)<a href="https://agentmods.dev/skills/receptron/mulmoclaude/mc-wiki-health-check"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-wiki-health-check/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-wiki-health-check"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-wiki-health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00085 | $0.00825 |
| Opus 5 | $0.00043 | $0.00413 |
| Sonnet 5 | $0.00017 | $0.00165 |
| Haiku 4.5 | $0.00009 | $0.00082 |
Grade A, and why
mc-wiki-health-check 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 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.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Health Check
A bundled MulmoClaude preset skill (mc- prefix = launcher-managed; do not edit
this file in the workspace, it is overwritten on every server boot).
This is the lint operation from the LLM-Wiki pattern: a periodic, fully
read-only sweep that flags drift in data/wiki/ (broken links, orphan
pages, tag mismatches, missing image / file refs) so the user can fix it
before it compounds. Findings only — this skill never writes to the wiki.
What to do
- Invoke
manageWikiwith{ "action": "lint_report" }. The server returns the structured report (re-uses the same lint helpers that power the on-demand "Wiki Lint" button). - Healthy wiki (zero findings): reply with one line — "Wiki is healthy (N pages checked)." — and stop. Do not page the user; the value of a weekly run is the silence on healthy weeks.
- Findings present: render a short, grouped report:
- Broken
[[page]]/links — listsource slug → targetwith the file path so the user can jump straight to the offending page. - Missing image / file refs — same shape.
- Orphan pages (no incoming links) — list slugs; suggest either linking
from
index.md/ a hub page, or archiving if obsolete. - Tag drift (tag in
index.md≠ tag in page frontmatter) — list the mismatches. Keep the prose minimal. The lint report's ownformatLintReportoutput is already terse and well-grouped; prefer pasting it over re-narrating.
- Broken
- Do not auto-fix. Each finding is a decision the user must make (rename vs delete, add a backlink vs archive, fix the tag in which place). Offer to fix any specific one if the user picks it up, but never write to the wiki as part of this scheduled run.
Rules
- Read-only: this skill never calls
manageWikiwithactionother thanlint_report. Any "fix" the user agrees to should be a follow-up turn so the boundary stays clear. - Quiet on success: a healthy wiki run ends in one line. Don't expand the report when there's nothing to report — the schedule's value is catching drift, not generating weekly noise.
- Don't open files unless asked: the lint output already names the offending slugs and paths. The user reads and decides; they'll ask to open a specific page if they want detail.
- Cadence: bundled schedule is
interval 168h(≈ weekly). The user can star this preset to opt in, or change the cadence by editing the re-registered task in/automationsafter activation.
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 · 62 lines · 85 tokens per session scan A 14a47abd9af5
mc-wiki-health-check is a skill published in the GitHub repository receptron/mulmoclaude (347 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 825 once invoked, about $0.0004 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.
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…