How do I install the Mnemos Codex skill?

Run npx skillmds@latest add tomevault-io/mnemos-codex in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mnemos Codex safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mnemos Codex?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mnemos Codex free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mnemos Codex?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mnemos Codex by tomevault-io — Agent Skill

Name: Mnemos Codex
Author: tomevault-io

Mnemos Codex

Use when Codex users or Codex agents need to install, configure, validate, troubleshoot, or operate Mnemos through MCP, or when they mention Codex memory, AGENTS.md memory policy, Codex Automations, or Mnemos in Codex.

tomevault-io 479dc8d 2 files · 3.2 KB Updated Sep 17, 2026

File contents

Mnemos for Codex

Use this skill to put Mnemos on the supported Codex path without overstating host automation. In Codex, the practical Mnemos workflow is:

recall at the start of substantial work
curate durable facts during or after the task
consolidate before finishing

Default path

Prefer pip install "mnemos-memory[mcp]" and mnemos ui.
Treat the blessed Codex setup as two parts: MCP config plus a repo-level AGENTS.md memory block.
Read references/install.md for install and validation.
Read references/operations.md for daily use, troubleshooting, and honest capability framing.

Claim discipline

Safe to claim: Mnemos works in Codex through MCP, shared MNEMOS_CONFIG_PATH, repo-level AGENTS.md, and optional maintenance Automations.
Do not claim built-in prompt/tool lifecycle hooks or Claude Code parity.
Hard auto-capture in Codex is host-dependent and not shipped by Mnemos today.

Daily loop

Start in recall mode: call mnemos_retrieve with a task-focused query and repo-scoped arguments.
Do the work, then switch to curator mode: store only durable facts with mnemos_store.
Use mnemos_inspect before storing a correction or when a retrieved memory looks suspicious.
Finish substantial work with mnemos_consolidate.
If Mnemos MCP tools are unavailable, continue normally instead of blocking work.

Recall mode

Use at the start of coding, debugging, review, or handoff tasks.
Query for architecture, current repo conventions, recent fixes, environment quirks, and user preferences that matter for this task.
In Codex, prefer current_scope=project, scope_id=<workspace or repo name>, and allowed_scopes=project,global.

Curator mode

Use during or near the end of a substantial task.
Store decisions, constraints, environment facts, recurring bug patterns, and stable preferences.
Skip one-off chatter, ephemeral plans, stack traces without reusable lessons, and secrets.

Avoid

Do not present Codex Automations as session capture.
Do not tell users to type memories manually as the primary workflow.
Do not market Codex as Tier 1 until real daily-use validation is complete.

Source: anthony-maio/mnemos — distributed by TomeVault.

---name: mnemos-codexdescription: Use when Codex users or Codex agents need to install, configure, validate, troubleshoot, or operate Mnemos through MCP, or when they mention Codex memory, AGENTS.md memory policy, Codex Automations, or Mnemos in Codex.---# Mnemos for CodexUse this skill to put Mnemos on the supported Codex path without overstating host automation. In Codex, the practical Mnemos workflow is:- recall at the start of substantial work- curate durable facts during or after the task- consolidate before finishing## Default path- Prefer `pip install "mnemos-memory[mcp]"` and `mnemos ui`.- Treat the blessed Codex setup as two parts: MCP config plus a repo-level `AGENTS.md` memory block.- Read `references/install.md` for install and validation.- Read `references/operations.md` for daily use, troubleshooting, and honest capability framing.## Claim discipline- Safe to claim: Mnemos works in Codex through MCP, shared `MNEMOS_CONFIG_PATH`, repo-level `AGENTS.md`, and optional maintenance Automations.- Do not claim built-in prompt/tool lifecycle hooks or Claude Code parity.- Hard auto-capture in Codex is host-dependent and not shipped by Mnemos today.## Daily loop1. Start in recall mode: call `mnemos_retrieve` with a task-focused query and repo-scoped arguments.2. Do the work, then switch to curator mode: store only durable facts with `mnemos_store`.3. Use `mnemos_inspect` before storing a correction or when a retrieved memory looks suspicious.4. Finish substantial work with `mnemos_consolidate`.5. If Mnemos MCP tools are unavailable, continue normally instead of blocking work.## Recall mode- Use at the start of coding, debugging, review, or handoff tasks.- Query for architecture, current repo conventions, recent fixes, environment quirks, and user preferences that matter for this task.- In Codex, prefer `current_scope=project`, `scope_id=<workspace or repo name>`, and `allowed_scopes=project,global`.## Curator mode- Use during or near the end of a substantial task.- Store decisions, constraints, environment facts, recurring bug patterns, and stable preferences.- Skip one-off chatter, ephemeral plans, stack traces without reusable lessons, and secrets.## Avoid- Do not present Codex Automations as session capture.- Do not tell users to type memories manually as the primary workflow.- Do not market Codex as Tier 1 until real daily-use validation is complete.---> Source: [anthony-maio/mnemos](https://github.com/anthony-maio/mnemos) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions