Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/jh941213/codex-lattice/plan-memory-hierarchy)<a href="https://agentmods.dev/skills/jh941213/codex-lattice/plan-memory-hierarchy"><img src="https://agentmods.dev/badge/skills/jh941213/codex-lattice/plan-memory-hierarchy.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.00543 |
| Opus 5 | $0.00017 | $0.00271 |
| Sonnet 5 | $0.00007 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
plan-memory-hierarchy 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layered Project Memory
This skill creates and maintains structured markdown memory files at project start, then reuses them during planning and execution.
Runtime Rules
- Confirm the project root. If unclear, ask the user.
- If
.plan-memory/does not exist, run bootstrap script.
python3 scripts/bootstrap_plan_memory.py --root . --project-name "<project-name>"
- Read core memory files:
.plan-memory/README.md.plan-memory/product/requirements.md.plan-memory/backend/requirements.md.plan-memory/frontend/requirements.md.plan-memory/shared/constraints.md
- Store new information in the most relevant layer file, not in a single aggregate file.
- Before final plan output, update
.plan-memory/README.mdsummary index.
Use Cases
- New project intake with requirements capture
- Splitting work by backend/frontend scope
- Long-running refactor/integration work requiring persistent context
스크립트 동작
Default directory tree
.plan-memory/
README.md
product/requirements.md
product/acceptance-criteria.md
backend/requirements.md
backend/api-contracts.md
backend/data-model.md
frontend/requirements.md
frontend/ux-flow.md
frontend/state-management.md
shared/constraints.md
shared/glossary.md
execution/current-plan.md
execution/open-questions.md
Key Rules
- Existing files are preserved by default; do not overwrite unless
--forceis passed. - For edits, ask for user confirmation before deleting/replacing existing docs.
- For new projects, fill
execution/current-plan.mdandproduct/acceptance-criteria.mdfirst.
Maintenance Rules
- Keep backend and frontend assumptions separate.
- Put cross-cutting rules (security/performance/compliance) in
shared/constraints.md. - Keep the summary index in
README.mdin sync with added layers/files. - End each planning pass by writing plan/risk/acceptance updates into
execution/current-plan.md.
스크립트 위치
/Users/kdb/.codex/skills/plan-memory-hierarchy/scripts/bootstrap_plan_memory.py
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 76 lines · 35 tokens per session scan A 0c7e7e248fb6
plan-memory-hierarchy is a skill published in the GitHub repository jh941213/codex-lattice (19 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 543 once invoked, about $0.0002 per session on Opus 5. 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.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.