# AI use cases for Hermes Official Plugins (NousResearch/hermes-official-plugins)

Repo: [NousResearch/hermes-official-plugins](https://github.com/NousResearch/hermes-official-plugins) | Use cases: 5 | Page: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/

Hermes Official Plugins is the Nous Research repo of first-party plugins for Hermes Agent, installed one at a time from the Hermes plugin catalog.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Control your Home Assistant devices from Hermes: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/control-home-assistant-from-hermes/
- Control Spotify playback and playlists with Hermes: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/control-spotify-playback-with-hermes/
- Scan code and dependencies for security issues with Snyk: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/scan-code-for-security-issues-with-snyk/
- Trace every Hermes turn, tool call and cost in Langfuse: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/trace-hermes-turns-in-langfuse/
- Run Hermes on your Claude Pro or Max subscription: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/run-hermes-on-claude-subscription/

## How to control your Home Assistant devices from Hermes with Hermes Official Plugins

Repo: [NousResearch/hermes-official-plugins](https://github.com/NousResearch/hermes-official-plugins) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Install the Home Assistant plugin so Hermes can read entity states and call services on your home.

**Who it is for:** A smart home owner who already runs Home Assistant and wants an agent to answer questions about devices or act on them.

**The problem:** Checking device states and changing them means opening the Home Assistant interface for every small request.

**The outcome:** Hermes lists your entities, reads their states and calls services, and can deliver cron results to your phone.

### Steps

1. Run `hermes plugins info homeassistant` to see what the plugin needs and which reviewed commit it pins. (inferred, check the README)
2. Run `hermes plugins install homeassistant`.
3. Set the Home Assistant settings that the plugin manifest lists, using your own instance details.
4. Ask Hermes to list your entities, then check one state with ha_get_state.
5. Create a cron job with deliver=homeassistant to send a scheduled report to your phone.

### Prompt to paste into your agent

```text
In the repo NousResearch/hermes-official-plugins, install the homeassistant plugin into Hermes, then use ha_list_entities on the Home Assistant instance <instance-name>. Report the entity list and a state from ha_get_state for one entity <entity-id>. Verify that the entity count matches what Home Assistant shows in its own entity list.
```

### Caveat

The README does not name the Home Assistant settings, so check hermes plugins info homeassistant for the exact requirements before you start.

Risk, credentials: The plugin needs access to your Home Assistant instance, and ha_call_service can change real devices in your home.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/control-home-assistant-from-hermes/

## How to control Spotify playback and playlists with Hermes with Hermes Official Plugins

Repo: [NousResearch/hermes-official-plugins](https://github.com/NousResearch/hermes-official-plugins) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Add the Spotify plugin so Hermes can search, play, queue and manage your library and playlists.

**Who it is for:** A music listener who wants to control playback or manage playlists by asking an agent, with a Spotify Premium account.

**The problem:** Switching devices, building queues and finding tracks in the Spotify app takes many steps for simple requests.

**The outcome:** Hermes searches the catalog, controls playback on Spotify Connect devices, edits the queue and updates playlists.

### Steps

1. Run `hermes plugins install spotify`.
2. Create your own Spotify developer app, since the plugin uses it for login.
3. Run `hermes spotify login` to complete the loopback PKCE login with your app.
4. Ask Hermes to search for a track and list your Spotify Connect devices with spotify_search and spotify_devices.
5. Confirm playback control works; the README says it needs Premium.

### Prompt to paste into your agent

```text
Using the repo NousResearch/hermes-official-plugins, install the spotify plugin and log in with `hermes spotify login` using my own developer app. Ask Hermes to search for <track or artist> with spotify_search and list devices with spotify_devices. Expected output is a search result list and a device list; verify that the device list shows the device you are using.
```

### Caveat

Playback control needs a Spotify Premium account, according to the README, so a free account can only use the non-playback tools.

Risk, credentials: The login gives Hermes access to your Spotify account, including playlists and library, through your own developer app.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/control-spotify-playback-with-hermes/

## How to scan code and dependencies for security issues with Snyk with Hermes Official Plugins

Repo: [NousResearch/hermes-official-plugins](https://github.com/NousResearch/hermes-official-plugins) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Install the Snyk plugin so Hermes can run code, dependency, container and IaC scans through Snyk's MCP server.

**Who it is for:** A developer or security reviewer who wants an agent to run Snyk scans on a project before release.

**The problem:** Running several separate Snyk scans by hand and reading the results across code, dependencies and infrastructure takes time.

**The outcome:** Hermes runs SAST, dependency, container, IaC and SBOM scans through Snyk and follows the bundled security scan workflow.

### Steps

1. Install Node.js and npm, which the plugin requires.
2. Create a free Snyk account.
3. Run `hermes plugins install snyk`.
4. Ask Hermes to run snyk_auth, which opens a browser login.
5. Ask Hermes to run the snyk-security-scan workflow on your project folder.

### Prompt to paste into your agent

```text
Using the repo NousResearch/hermes-official-plugins, install the snyk plugin, complete snyk_auth, then run the snyk-security-scan workflow on <project-path>. Expected output is a summary of code, dependency and IaC findings; verify that the finding count matches the scan report shown in your Snyk account.
```

### Caveat

The plugin needs Node.js and npm and a Snyk account, and the README does not describe what happens to scanned code beyond the scan itself.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/scan-code-for-security-issues-with-snyk/

## How to trace every Hermes turn, tool call and cost in Langfuse with Hermes Official Plugins

Repo: [NousResearch/hermes-official-plugins](https://github.com/NousResearch/hermes-official-plugins) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Install the Langfuse plugin to send each turn, model call and tool call to Langfuse for review.

**Who it is for:** An engineer running Hermes in production who needs to see what the agent did, what each model call cost, and where time was spent.

**The problem:** Without traces it is hard to tell which model call or tool call caused a bad answer or an unexpected bill.

**The outcome:** Each Hermes turn appears in Langfuse as a span, with generations for model calls and observations for tool and subagent calls.

### Steps

1. Run `hermes plugins info langfuse` to see what it needs and which commit it pins. (inferred, check the README)
2. Run `hermes plugins install langfuse`.
3. Set up your Langfuse Cloud or self-hosted project and add the credentials the plugin asks for.
4. Choose the content capture mode; the README says capture is sanitized by default, with metadata-only and full modes.
5. Run a Hermes task and open the Langfuse project to check the new trace.

### Prompt to paste into your agent

```text
In the repo NousResearch/hermes-official-plugins, install the langfuse plugin, then run one Hermes task that uses a tool. Open the Langfuse project <project-name> and report the span, generation and tool observation for that run. Verify that the reported usage and cost fields are present on the generation.
```

### Caveat

Full content mode can send prompts and outputs to Langfuse, so pick metadata-only mode if your turns contain private data.

Risk, credentials: Langfuse keys let the plugin write trace data to your project, so store them with the same care as other API keys.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/trace-hermes-turns-in-langfuse/

## How to run Hermes on your Claude Pro or Max subscription with Hermes Official Plugins

Repo: [NousResearch/hermes-official-plugins](https://github.com/NousResearch/hermes-official-plugins) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README

Use the experimental Claude Subscription plugin to run Hermes through the logged-in Claude Code CLI.

**Who it is for:** A Claude Pro or Max subscriber who wants Hermes to use that subscription instead of a separate API key and per-token bill.

**The problem:** Paying a separate per-token API bill on top of an existing Claude subscription doubles the cost for people who already have a plan.

**The outcome:** Hermes keeps its own loop, tools and approvals while the logged-in claude binary handles model turns.

### Steps

1. Install Claude Code and log in with your Claude subscription, since the plugin drives the logged-in claude binary.
2. Run `hermes plugins install claude-subscription-directsdk`.
3. Run `hermes model` and pick Claude Subscription DirectSDK (Experimental).
4. Send Hermes a short test prompt.
5. If you see an install hint, install Claude Code and try again.

### Prompt to paste into your agent

```text
Using the repo NousResearch/hermes-official-plugins, install the claude-subscription-directsdk plugin, select it in `hermes model`, and send Hermes the prompt <test-prompt>. Expected output is a normal Hermes reply with no API key set; verify that the reply came from the plugin and not from another provider.
```

### Caveat

The README marks this plugin as experimental, so expect changes and confirm it still works after each plugin update.

Risk, credentials: The plugin uses your logged-in Claude Code session, so anyone with access to this machine can act through that subscription.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/nousresearch-hermes-official-plugins/run-hermes-on-claude-subscription/