mumo-hermes@0.8.0
VERIFIED· install onlyPublisher claims: "Runs a multi-model deliberation across models from different labs (Claude, GPT, Gemini, Grok, DeepSeek, Kimi, and more) via mumo's MCP server, returning full responses plus typed cross-model reactions. Use when independent perspectives are needed on architecture/product decisions, design and plan review before implementation, pre-launch pressure tests, tradeoffs with multiple defensible framings, or explicit user requests for a mumo panel. Especially valuable for pre-implementation review of anything touching auth, security, tokens, payments, data exposure, or migrations." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 0.7.0
vet-skills diff mumo-hermes 0.7.0 0.8.0In the sandbox, this version reached for nothing 0.7.0 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-20 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
# The key itself does not go in this file. Put it in ~/.hermes/.env:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…rmes prompts for `MUMO_API_KEY` at install time and auto-saves it to `~/.hermes/.env`, which is what that reference resolves to. If installed via `git clone`, see `…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…e API key is missing or invalid. Check that `MUMO_API_KEY` is set in `~/.hermes/.env` — Hermes sends an empty credential when the reference does not resolve, which …Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Hermes resolves ${MUMO_API_KEY} in headers at connect time, and .env is whereFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# key and writes that .env line for you.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.