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 skills add pyros-projects/limitless --skill memory-helpgit clone --depth 1 https://github.com/pyros-projects/limitlessWrote 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/pyros-projects/limitless/memory-help)<a href="https://agentmods.dev/skills/pyros-projects/limitless/memory-help"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/memory-help/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pyros-projects/limitless/memory-help"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/memory-help.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.03560 |
| Opus 5.5 | $0.00034 | $0.01424 |
| Sonnet 5.5 | $0.00017 | $0.00712 |
| Haiku 4.5 | $0.00009 | $0.00356 |
Grade A, and why
memory-help 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 yesterday.
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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Help
BETA — This memory system is in active testing. If you encounter bugs, confusing behavior, or have suggestions, run:
codies-memory feedback "describe what happened" --agent <name>— your feedback is saved and reviewed.
For installation or migration, follow INSTALL.md: native
plugins provide the skills, and uv tool installs the CLI separately. Run
codies-memory from the user's project directory; codies-memory --version
identifies the backend in use.
What This System Is
You have a persistent file-based memory system. It stores what you learn, observe, and decide across sessions. Your vault lives at ~/.memory/<your-agent-name>/. Memory commands require --agent <your-agent-name>; --version and --help do not.
There are two scopes:
- Global — knowledge that applies across all projects (your identity, cross-project lessons, reflections)
- Project — knowledge specific to one project (observations, decisions, session summaries)
There are also two practical operating modes:
- Standalone mode — works with the canonical vault only
- Full mode — recommended: canonical vault plus QMD retrieval
QMD is recommended when available because recall becomes faster, more token-efficient, and semantic across multiple memory stores. If the user wants that full mode and does not have QMD yet, offer to help install it.
Concepts
Read this section carefully. These terms have specific meanings in this system.
Record Types
| Type | What it is | Scope | When to create |
|---|---|---|---|
| inbox | A raw observation or note. Unprocessed. | project | When you notice something worth remembering but haven't decided what it means yet. Use capture. |
| thread | An ongoing investigation or topic you're tracking across sessions. | project or global | When an inbox item keeps coming up, or you're tracking something over time. Promote from inbox. |
| lesson | A reusable pattern or rule you've learned. "When X, do Y." | project or global | When you've learned something actionable that applies beyond the current moment. Promote from inbox or thread. |
| decision | A choice that was made with rationale. | project or global | When a significant decision happens and you want to remember why. |
| session | A summary of one work session. | project or _general |
At the end of every session. If no project vault resolves, it lands in _general. |
| daily-log | Auto-generated append-only cross-project activity index. | global only | Do not create or edit manually. create and capture append entries automatically. |
| reflection | Philosophical or meta-level thinking. | global only | When you want to process what something meant, not just what happened. |
| dream | Emotional/subconscious processing. | global only | Optional. For agents that use creative processing. |
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.
- yesterday Changed 1f6431d1d490
- 3d ago Changed · +13 lines 9465d9e4858d
- 8d ago Changed · +21 lines fa1850113190
- 22d ago Changed · +13 lines 67cb26f5553e
- 1mo ago First seen · 321 lines · 86 tokens per session scan A c7bfc947e704
memory-help is a skill published in the GitHub repository pyros-projects/limitless (2 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 3,560 once invoked, about $0.0003 per session on Opus 5.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
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
adr-ops
Author, index, and lint Architecture Decision Records — append-only memory that recovers the WHY behind a system's shape. Triggers on: adr, architecture decision record, decision log, record this decision, supersede an adr, why was this decided, adr template, next adr number.
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
memory-prune
Manual reviewable prune of stale memory entries. Lists project entries older than 30 days with content preview; Frank decides per-entry [keep | archive | pin]. Keeps MEMORY.md under the auto-load 200-line truncation. Use when MEMORY.md exceeds 180 lines or session-end after a heavy work week.