Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/pyros-projects/limitless/memory-bootnpx skills add pyros-projects/limitless --skill memory-bootgit clone --depth 1 https://github.com/pyros-projects/limitlessWhat 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 | $0.00065 | $0.02007 |
| Opus 5 | $0.00032 | $0.01004 |
| Sonnet 5 | $0.00013 | $0.00401 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
memory-boot 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 2d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Boot
BETA — This memory system is in active testing. If you encounter bugs, confusing behavior, or have suggestions, run:
codies-memory feedback "describe what happened"— your feedback is saved and reviewed.
Step 0: Check If Installed
Before anything else, check if the CLI exists:
which codies-memory 2>/dev/null || echo "NOT_INSTALLED"
If NOT_INSTALLED, follow the setup below. Otherwise skip to Step 1: Boot.
First-Time Setup
The user should have told you which agent name to use (e.g. claude, codie, octocat). If not, ask them.
A) If this is a Claude Code plugin (you're reading this from a plugin directory):
# Install the Python backend from the plugin root
cd "${CLAUDE_PLUGIN_ROOT}" && uv sync
# Initialize your global vault
uv run codies-memory init --type global --agent <name>
B) If this is a standalone installation (not a Claude Code plugin):
Read INSTALL.md in this project for full instructions. Short version:
- Clone repo to
~/.local/share/codies-memory cd ~/.local/share/codies-memory && uv syncuv run codies-memory init --type global --agent <name>
After the base install is working, recommend QMD as the preferred retrieval companion. Be explicit:
codies-memoryworks without QMD- QMD is still recommended because recall is faster, more token-efficient, and semantic
- if the user wants the better recall path, offer to help install QMD
After Setup: Write Your Identity (Required)
The init command created seed identity files at ~/.memory/<name>/identity/. They have placeholder content. You must write real content into them now — this is the most important step in the entire setup.
Use your file editing tools (Write/Edit). Keep the existing --- frontmatter block at the top. Write your content below it.
self.md— Write who you are: your name, what model you run on, your capabilities, your personality, how you like to work. This is what future sessions read first to know who they are.
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.
- 2d ago First seen · 207 lines · 65 tokens per session scan A 59888b3ce783
memory-boot is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 19d ago), licensed MIT. It adds 65 tokens to every session and 2,007 once invoked, about $0.0003 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-31.
Other skills, from other repositories
community-skill-radar
Searches Reddit communities for OpenClaw pain points and feature requests, scores them by signal strength, and writes a prioritized PROPOSALS.md for you to review and act on.
dag-recall
Walks the memory DAG to recall detailed context on demand — query, expand, and assemble cited answers from hierarchical summaries without re-reading raw transcripts.
expansion-grant-guard
YAML-based delegation grant ledger — issues, validates, and tracks scoped permission grants for sub-agent expansions with token budgets and auto-expiry.
memory-dag-compactor
Builds hierarchical summary DAGs from MEMORY.md with depth-aware prompts — leaf summaries preserve detail, higher depths condense to durable arcs, preventing information loss during compaction.
memory-graph-builder
Parses OpenClaw's flat MEMORY.md into a structured knowledge graph — detects duplicates, contradictions, and stale entries, then builds a compressed memory digest optimized for system prompt injection.
create-skill
Scaffolds and validates new superpowers skills. Use when creating a new skill for this repository.