Case 02222
A fast, offline static risk analysis CLI for AI agent skill files. Detects malicious instructions, steganographic payloads, and dangerous capability chains.
npx -y skills add knownasnaffy/prompthound --skill case_02222Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Installs and manages Scope-Based Memory and Automated REM Sleep (memory consolidation) for OpenClaw agents. Use this skill when an agent's MEMORY.md is bloated, when the user asks to implement "REM Sleep", "memory decay", or "scoped memory", or to organize an agent's memory into domain-specific topics to save context window tokens.
SKILL.md
2.8 KB, 593 tokens by cl100k_base, as published. Nobody here has run it
Scoped Memory Manager
This skill upgrades an OpenClaw agent's memory architecture from a single, bloated MEMORY.md to a Scope-Based Memory system with automated REM Sleep (memory consolidation and decay).
Architecture
- Global Router (
MEMORY.md): Kept extremely lean. Only contains core identity, active focus, and an index of domain-specific memory files. - Domain-Specific Memory (
memory/topics/*.md): Stores hyper-specific rules, constraints, and knowledge (e.g.,shopify.md,rails.md). Retrieved dynamically viamemory_searchandmemory_getonly when relevant. - Automated REM Sleep: A scheduled background job (cron) that wakes up an isolated agent to compress daily logs, extract new patterns, prune outdated "trauma" constraints, and file the distilled knowledge into the correct topic files.
Installation & Setup
When the user asks to install or configure scoped memory / REM sleep, follow these steps:
1. Scaffold the Directory Structure
Run the setup script to create the necessary directories:
sh scripts/setup.sh
2. Schedule the REM Sleep Cron Job
Use the cron tool to schedule the weekly consolidation job.
Call the cron tool with action: "add" and the following payload:
- name: "Memory REM Sleep (Consolidation)"
- schedule:
{ "kind": "cron", "expr": "0 3 * * 0" }(Sundays at 3:00 AM) - sessionTarget: "isolated"
- delivery:
{ "mode": "announce" } - payload:
{ "kind": "agentTurn", "message": "It is time for your weekly REM sleep cycle. Please read the current `MEMORY.md` and the daily log files (`memory/YYYY-MM-DD.md`) from the past 7 days. Your task is to perform memory consolidation: \n1. Extract new patterns and important context from the logs.\n2. Review `MEMORY.md` and prune obsolete rules or constraints.\n3. Move domain-specific knowledge into the appropriate `memory/topics/*.md` files.\n4. Rewrite `MEMORY.md` to be a concise global router.\n5. Summarize what was added, moved, and forgotten." }
3. Migrate Existing Memory
If the agent already has a bloated MEMORY.md, proactively offer to read it and partition the content into memory/topics/*.md files right now.
Usage Guidelines
- Remind users that
MEMORY.mdis NOT for storing everything. - When learning a new specific framework, proactively create a new topic file in
memory/topics/instead of polluting the globalMEMORY.md.