Arnie016/codex-prompt-templates / skills/agent-memory-ledger
agent-memory-ledger
VerifiedCreate or use lightweight persistent project memory for Codex. Use when the user wants Codex to remember decisions, naming, architecture rules, progress, experiment results, or prior debugging across sessions. Also use with memsearch-style markdown memory.
Agent Memory Ledger
Use markdown as the durable source of truth. Semantic indexes are optional derived caches.
Default Files
Create only the files needed:
.codex-memory/
decisions.md
architecture.md
glossary.md
experiments.md
todo.md
Entry Format
## 2026-05-19 - Short Title
- Context:
- Decision:
- Evidence:
- Follow-up:
Recall Workflow
- Search
.codex-memory/, project docs, and recent task briefs. - If
.memsearch/memory/exists andmemsearchis installed, prefer$auto-skill-build-memsearch-codex-memoryfor progressive recall. - Return a short answer with source file/date.
- Update memory only for stable decisions, not every transient observation.
Rules
- Do not store secrets.
- Do not store full logs unless they are compacted.
- Keep each memory file skimmable; archive old details into dated files.
- Prefer "why we chose X" over "we talked about X".
Use with $low-token-context for long projects.
Validation
- Memory entries cite a source file, command result, or user decision.
- Secrets and raw bulky logs are not stored.
- A future session can answer "what changed and why?" from the memory files.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |