omo/lazycodex: The coding agent for tokenmaxxers;the one and only agent harness for complex codebases. For your Codex, for your OpenCode
memory-management
memory-management is an open-source workflow skill for Claude Code and compatible agents, published by ThinkInAIXYZ. Its author describes it as: “Guide the agent to recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape.”. The project has 6.2k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/memory-management`.
What memory-management does
Use this skill when a task may produce durable learning or when the user asks you to recall, remember, continue earlier work, preserve an exact statement, capture a reusable procedure, or handle a recurring need.
Installation
Add memory-management to your agent with:
git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/memory-managementAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for memory-management is organised into these sections:
- Recall
- Remember
- Verbatim Scope
- Procedures -> Skill
- Recurring -> Scheduled Task
- End-of-task Learning Check
When to use it
Reach for memory-management when you want workflow help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear Apache-2.0 license — safe to read and adapt
- Ships in ThinkInAIXYZ/deepchat, an established project with 6,228 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does memory-management do?
- Guide the agent to recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape.
- How do I install memory-management?
- Run git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/memory-management in your agent, then reload your skills. Review the source at https://github.com/ThinkInAIXYZ/deepchat before installing.
- Is memory-management free to use?
- Yes. memory-management is free and open source under the Apache-2.0 license, so you can read, run, and adapt it within that license's terms.
- Where does memory-management come from?
- memory-management ships inside ThinkInAIXYZ/deepchat, a repository that contains 25 catalogued skills in total. The repository's 6,228 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Workflow →Binding ultrawork mode directive for omo-senpi. When a prompt contains ultrawork or ulw, the omo input hook injects the full directive as a hidden custom message (customType omo-ultrawork:directive, display false) ahead of the user's text, which is left untouched; a prompt queued while the agent is streaming instead carries the directive appended inside that same message. The directive is present in the conversation context; on the idle path it is not shown in the visible prompt, while a queued prompt carries the directive visibly (exactly as before this change). When the directive is already present in the conversation, do not read this file again - this file is that same directive. Read this file only when ultrawork mode is requested and the directive is not already present in the conversation.
Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.
Team-first maximum-saturation research orchestration for omo-senpi. Scopes solo, ALWAYS asks which final format to render (PDF+DOCX default), then stands up a max-size cooperating team (team_create): one member per axis plus skeptic/red-team members for ultradebate/hyperdebate cross-critique, explore/librarian lanes, live ulw-loop journaling, an EXPAND loop until leads run dry, claims proven by code or the claim-graph gate, and a cited synthesis with charts/Mermaid/assets behind visual-QA and `writing` proofread gates. ACTIVATES ONLY on an explicit user demand for research: the word 'ulw-research' ('/ulw-research', '$ulw-research'), any 'ulw' research wording, 'ultradebate' or 'hyperdebate' research requests, or an explicit request for research / deep research / an ultra-precise investigation, in any language. Never self-activates for ordinary questions, debugging, or implementation context-gathering. While active it overrides exploration-bounding defaults: exhaustive coverage is the goal.
Persistent Codex-style goal tracking for pi. Use when the user explicitly asks to set, continue, audit, pause, resume, complete, or inspect a long-running goal.