MukundaKatta

Hermes Agentmemory — Security skill for Claude Code

Security community

Pull-model episodic memory plugin for Hermes Agent.

How to install Hermes Agentmemory

This entry records only its repository, not the path inside it, so there is no exact command to give. Open MukundaKatta/hermes-agentmemory and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Hermes Agentmemory does

Pull-model episodic memory plugin for Hermes Agent. Real deletes, audit trace, BYO Claude. MIT.

Alternatives in Security

Pal — Multi-model AI integration — chat, debugging, code review, planning, security audit 11.3k ★
Token Scan — Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP l 3.8k ★
Skill Coverage Audit — Trace codepaths in diffs, map against tests, auto-generate missing coverage — use before shipping PRs 2.8k ★

README

hermes-agentmemory

[![test](https://github.com/MukundaKatta/hermes-agentmemory/actions/workflows/test.yml/badge.svg)](https://github.com/MukundaKatta/hermes-agentmemory/actions/workflows/test.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![Python](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)

A drop-in [Hermes Agent](https://github.com/NousResearch/hermes-agent) memory plugin built on [agentmemory](https://github.com/MukundaKatta/agentmemory).

Pull-model episodic memory with real deletes and an audit trace. The point: Hermes Agent is good at remembering. This plugin gives it a memory layer that takes deletion seriously.

Why another memory plugin?

Hermes ships with several first-class memory backends (Mem0, Honcho, Hindsight, etc.). They consolidate in the background, which is the dominant pattern in agentic memory right now. That makes recall cheap and fast at the cost of two things:

Deletes are not always real. Once an episode is baked into a derived summary, removing the original event leaves the summary intact.
Memory injection is opaque. Background prefetch happens off the hot path; the user does not see exactly which past events were used until something goes wrong.

`agentmemory` flips both. It does no background work, every write is synchronous, deletes are immediate and complete, and every prefetch writes a trace record (`event_ids` + `summary` + `prompt`) to `$HERMES_HOME/agentmemory/trace.jsonl` so the user can audit what entered the prompt.

Install

This is a **standalone memory plugin**. Hermes Agent stopped accepting new built-in memory providers — see [CONTRIBUTING.md](https://github.com/NousResearch/hermes-agent/blob/main/CONTRIBUTING.md#memory-providers-ship-as-a-standalone-plugin). The official path is to drop the plugin into the user-plugins directory that Hermes discovers automatically.