For connecting session starts, session ends, and submitted prompts to Mnemos. The description does not explain what Mnemos stores or does with them.

They automate Mnemos updates around the main points in an agent session instead of requiring manual commands.

How s60yucca/mnemos configures Claude Code

mnemos: Settings file for Claude Code

.claude/settings.json

mnemos is a settings file for Claude Code from s60yucca/mnemos. Its token cost is not measured, scanned A, original, MIT.

Agent settings that run Mnemos commands when a session starts or ends and whenever you submit a prompt. Mnemos is the external program named in those commands.

In plain words

What is it for?: For connecting session starts, session ends, and submitted prompts to Mnemos. The description does not explain what Mnemos stores or does with them.
Why use it?: They automate Mnemos updates around the main points in an agent session instead of requiring manual commands.

Written for Claude Code: SessionEnd hook event.

This is s60yucca/mnemos's own configuration. It tells Claude Code how to work on mnemos itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mnemos configures →

One of 4 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 3 are separate, each on its own page.

Reuse

Borrowing it

Nothing to install: this file belongs to s60yucca/mnemos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/s60yucca/mnemos/main/.claude/settings.json

Clone the repo

git clone --depth 1 https://github.com/s60yucca/mnemos

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/settings/s60yucca/mnemos/settings/github.svg)](https://agentmods.dev/settings/s60yucca/mnemos/settings)

Your own site

<a href="https://agentmods.dev/settings/s60yucca/mnemos/settings"><img src="https://agentmods.dev/badge/settings/s60yucca/mnemos/settings/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.

Your own site · 80×15

<a href="https://agentmods.dev/settings/s60yucca/mnemos/settings"><img src="https://agentmods.dev/badge/settings/s60yucca/mnemos/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

mnemos 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 2mo 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.

.claude/settings.json · 35 lines

What it actually says

{
  "hooks": {
    "SessionEnd": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "mnemos hook session-end"
          }
        ]
      }
    ],
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "mnemos hook session-start"
          }
        ]
      }
    ],
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "mnemos hook prompt-submit"
          }
        ]
      }
    ]
  }
}

Same file

What else `settings.json` configures

This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

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.

2mo ago First seen · 35 lines scan A d5ee93796af9

Subscribe to this mod's changes

mnemos is a settings file published in the GitHub repository s60yucca/mnemos (23 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

mnemos next to 6 settings from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mnemoss60yucca/mnemos	Settings file	23	3mo ago	MIT	A	—	Claude Code
supabasesupabase/supabase	Settings file	115k	yesterday	Apache-2.0	A	—	Claude Code
supersetapache/superset	Settings file	75k	today	Apache-2.0	A	—	Claude Code
RuViewruvnet/RuView	Settings file	103k	yesterday	MIT	A	—	Claude Code
claude-cookbooksanthropics/claude-cookbooks	Settings file	54k	2d ago	MIT	A	—	Claude Code
ormprisma/orm	Settings file	48k	yesterday	Apache-2.0	A	—	Claude Code
claude-code-best-practiceshanraisshan/claude-code-best-practice	Settings file	69k	yesterday	MIT	A	—	Claude Code