Install
$ agentstack add skill-akin-lvyifang-codex-memory-lite-codex-memory-bootstrap ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Codex Memory Bootstrap
Initialize a structured project memory layer for long-running collaboration so work no longer depends on a single handoff file.
Pre-Write Checks
Before creating .codex-memory/, first define an absolute path variable: PROJECT_ROOT.
PROJECT_ROOTmust be the project root for the current session- Do not treat
~,/,~/.config/opencode,~/.codex, a skills directory, or a config directory as the project root - If the current directory does not look like a project directory, or the project root is still unclear, stop and confirm it before creating anything
- All directories and files must be created under
{PROJECT_ROOT}/.codex-memory/ - Do not treat the bare relative path
.codex-memory/as the final target path
When To Use
Use this when any of the following is true:
- The user explicitly says "Initialize this project's memory"
- The work will continue across multiple sessions
- The work spans multiple files, pages, or topics
- The project already has handoff, rule, or history buildup
- The current thread is visibly getting bloated
Natural Trigger Phrases
- Initialize this project's memory
Goal
Create the smallest usable .codex-memory/ structure and establish or update the project-level AGENTS.md.
Specifically:
- if the project does not have
AGENTS.md, create the full file fromtemplates/project-agents.md - if the project already has
AGENTS.md, update only the managedCODEX-MEMORYblock - after writing, always run validation so
AGENTS.mdis confirmed against the full template or the managed-block template
Workflow
- Check whether
.codex-memory/already exists at the project root. - If it does not exist, create the following structure:
.codex-memory/
├── current.md
├── spec/
│ ├── index.md
│ ├── design-rules.md
│ ├── frontend-design-standards.md
│ ├── frontend-page-workflow.md
│ ├── component-reuse.md
│ └── workflow-rules.md
├── tasks/
│ ├── index.md
│ ├── active/
│ └── archive/
└── archive/
- Write the standard templates into those files.
- Handle project-level
AGENTS.md:
- if
AGENTS.mddoes not exist, create the full file fromtemplates/project-agents.md - if
AGENTS.mdalready exists, only append or update the managedCODEX-MEMORYblock defined bytemplates/project-agents-block.md
- Run validation:
- freshly created full file:
python3 scripts/validate_project_agents.py --project-root --mode create - managed-block update on an existing file:
python3 scripts/validate_project_agents.py --project-root --mode update
- If the project contains an older handoff file such as
codex-handoff.md, record it as "pending migration", but do not delete it automatically. - Report the initialization result:
- the
PROJECT_ROOTused this time - created directories
- created files
- whether
AGENTS.mdwas created or updated AGENTS.mdvalidation result- whether an old handoff was found
- whether migration should be recommended next
Templates And Validation
- full project-level
AGENTS.mdtemplate:templates/project-agents.md - managed block template:
templates/project-agents-block.md - validation script:
scripts/validate_project_agents.py
Validation requirements:
AGENTS.mdmust existCODEX-MEMORY:START / ENDmust each appear exactly once- if the file was newly created, it must match
templates/project-agents.md - if the file already existed, its managed block must match
templates/project-agents-block.md
Remind The User After Initialization
- This project now has
.codex-memory/enabled - Future sessions should read
current.mdfirst - Project-level
AGENTS.mdwas created from template or updated by managed block and passed validation - If an old handoff exists, migrate it instead of maintaining both systems in parallel
Constraints
- Do not automatically delete old handoff files
- Do not migrate legacy content during bootstrap without an explicit migration step
- Do not dump historical process notes straight into
current.md - Do not freely improvise a new project-level
AGENTS.md; usetemplates/project-agents.md - Do not skip validation after writing
AGENTS.md - Do not create any
.codex-memory/directories or files beforePROJECT_ROOTis confirmed
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: AKin-lvyifang
- Source: AKin-lvyifang/codex-memory-lite
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.