Hermes Agent is an AI assistant that learns from its use by creating and improving skills, retaining knowledge, searching past conversations, and adapting to its users. It is for people who want to run an agent through a terminal or messaging platforms while connecting it to different AI models and scheduled tasks.
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 NousResearch/hermes-agent --skill google_meetgit clone --depth 1 https://github.com/NousResearch/hermes-agentWrote 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/nousresearch/hermes-agent/google_meet)<a href="https://agentmods.dev/skills/nousresearch/hermes-agent/google_meet"><img src="https://agentmods.dev/badge/skills/nousresearch/hermes-agent/google_meet/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/nousresearch/hermes-agent/google_meet"><img src="https://agentmods.dev/badge/skills/nousresearch/hermes-agent/google_meet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 3 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 Privilege Escalation · line 66 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Privilege Escalation · line 53 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 63 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00057 | $0.01802 |
| Opus 5.5 | $0.00023 | $0.00721 |
| Sonnet 5.5 | $0.00011 | $0.00360 |
| Haiku 4.5 | $0.00006 | $0.00180 |
Grade B, and why
google_meet scanned grade B with 1 finding 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 29d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
`hermes meet install --realtime` prompts before running `sudo apt-get` (Linux) Copies of this mod
7 near-identical copies found in the catalogue:
- google_meet — 100% identical, 9 lines differ
- google_meet — 100% identical, 0 lines differ
- google_meet — 100% identical, 9 lines differ
- google_meet — 100% identical, 9 lines differ
- google_meet — 100% identical, 9 lines differ
- google_meet — 100% identical, 9 lines differ
- google_meet — 100% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
google_meet
When to use
The user says any of:
- "join my Meet at "
- "take notes on this meeting"
- "summarize the meeting and send followups"
- "sit in on my standup"
- "be a bot in this call and speak up when X"
Two modes
| Mode | What the bot does |
|---|---|
transcribe (default) |
Joins, enables captions, scrapes a transcript. Listen-only. |
realtime |
Same as transcribe PLUS speaks into the meeting via OpenAI Realtime. The agent calls meet_say(text) and the bot's voice comes out of the call. |
Pick realtime only when the user actually wants the agent to speak. It costs real money (OpenAI Realtime is pay-per-audio-minute) and requires a virtual audio device set up on the machine running the bot.
Two locations
| Location | When |
|---|---|
| Local (default) | Gateway machine runs the Playwright bot directly. |
Remote node (node="<name>") |
Bot runs on a different machine that has a signed-in Chrome and (for realtime) a configured audio bridge. Useful when the gateway runs on a headless Linux box but the user's real signed-in Chrome lives on their Mac. |
Prerequisites the user must handle once
Easiest path — run the built-in installer:
hermes plugins enable google_meet
hermes meet install # PM dependencies + Chromium (transcribe only)
hermes meet install --realtime # + pulseaudio-utils / brew blackhole+ffmpeg
hermes meet auth # optional; skips guest-lobby wait
hermes meet setup # preflight checks
hermes meet install --realtime prompts before running sudo apt-get (Linux)
or brew install (macOS). Pass --yes to skip the prompt. It will NOT touch
your macOS default-input setting — you have to select BlackHole 2ch in
System Settings yourself before starting a realtime meeting.
For manual realtime audio setup:
# Linux: sudo apt install pulseaudio-utils
# macOS: brew install blackhole-2ch ffmpeg
# → System Settings → Sound → Input → BlackHole 2ch
# Then set OPENAI_API_KEY or HERMES_MEET_REALTIME_KEY in ~/.hermes/.env
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- __init__.py 2.8 KB runs code
- _jsonfile.py 1.1 KB runs code
- audio_bridge.py 5.2 KB runs code
- cli.py 12 KB runs code
- meet_bot.py 24 KB runs code
- node/__init__.py 1.1 KB runs code
- node/cli.py 3.7 KB runs code
- node/client.py 2.9 KB runs code
- node/protocol.py 3.5 KB runs code
- node/registry.py 2.5 KB runs code
- node/server.py 5.5 KB runs code
- plugin.yaml 719 B
- process_manager.py 8.0 KB runs code
- README.md 7.1 KB
- realtime/__init__.py 201 B runs code
- realtime/openai_client.py 9.0 KB runs code
- tools.py 7.9 KB runs code
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.
- 29d ago Changed · -3 lines ebb8d8ce8267
- 1mo ago First seen · 149 lines · 57 tokens per session scan B e1f179bed4a0
google_meet is a skill published in the GitHub repository NousResearch/hermes-agent (256,529 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,802 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
keybindings-help
Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify /.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
Read or triage email, clean up an inbox, draft or send messages, and check delivery. Use for the user's connected mailbox or your own email, including questions about its availability; choose the correct sender and follow the confirmation policy.
manage-settings
Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool first. Never use for repository, app, eval, or other non-Muse configuration.
read-session
Locate and read Muse Code's OWN session logs — the current session or a prior one. Use when the user asks to pull context from, continue, summarize, or inspect a previous Muse Code session, asks to restore or recover work that was lost, wiped, or overwritten and might survive in an earlier session's log, references an…
device_data
Read cached contacts and calendar events from Muse storage. Delete Muse's local copy of either source without modifying paired devices.