助记符法典
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# 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
1. 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).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
章节与文件索引
按说明文件中的顺序排列。
默认路径
主张纪律
每日循环
调用模式
策展人模式
文件/命令 -> pip install "mnemos-memory[mcp]" · mnemos ui · AGENTS.md · references/install.md · references/operations.md · MNEMOS_CONFIG_PATH · mnemos_retrieve · mnemos_store
内容校验值 -> b24ecd650de6
当前原文的自动摘译,尚未人工审校。
默认路径
更喜欢
pip install "mnemos-memory[mcp]"和mnemos ui。将受祝福的 Codex 设置视为两部分:MCP 配置加上存储库级别的AGENTS.md内存块。阅读references/install.md进行安装和验证。阅读references/operations.md了解日常使用、故障排除和诚实的能力框架。主张纪律
安全声明:Mnemos 通过 MCP、共享
MNEMOS_CONFIG_PATH、回购级别AGENTS.md以及可选的维护自动化在 Codex 中工作。不要声称内置提示/工具生命周期挂钩或克劳德代码奇偶校验。 Codex 中的硬自动捕获取决于主机,目前 Mnemos 尚未提供。每日循环
从调用模式开始:使用以任务为中心的查询和存储库范围的参数调用
mnemos_retrieve。完成工作,然后切换到管理者模式:使用mnemos_store仅存储持久事实。在存储更正之前或当检索到的记忆看起来可疑时使用mnemos_inspect。使用mnemos_consolidate完成大量工作。如果 Mnemos MCP 工具不可用,请正常继续而不是阻止工作。调用模式
在编码、调试、审查或移交任务开始时使用。查询与此任务相关的体系结构、当前存储库约定、最近的修复、环境怪癖和用户首选项。在 Codex 中,优先选择
current_scope=project、scope_id=<workspace or repo name>和allowed_scopes=project,global。策展人模式
在一项重要任务期间或接近结束时使用。存储决策、约束、环境事实、重复出现的错误模式和稳定的偏好。跳过一次性的闲聊、短暂的计划、没有可重复使用的课程和秘密的堆栈跟踪。