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-capturegit 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-capture)<a href="https://agentmods.dev/skills/pyros-projects/limitless/memory-capture"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/memory-capture/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-capture"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/memory-capture.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.00069 | $0.00898 |
| Opus 5.5 | $0.00028 | $0.00359 |
| Sonnet 5.5 | $0.00014 | $0.00180 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
memory-capture 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 12d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Capture
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.
When To Use
When you want to persist anything:
- An observation during work -> inbox
- A lesson learned -> lesson
- An architecture decision -> decision
- A philosophical reflection -> reflection
- A dream narrative -> dream
- Past memories from basic-memory or other sources -> any type with provenance
Type Inference
If you don't specify a type, the system infers from content:
| Signal | Inferred Type |
|---|---|
| "I learned...", actionable pattern | lesson |
| "We decided...", formed conclusion | decision |
| Philosophical, emotional processing | reflection |
| Surreal imagery, narrative fragments | dream |
| Active investigation, open question | thread |
| Everything else | inbox |
Scope Routing
- Global types (reflection, dream, skill, playbook) -> global vault (resolved via
--agentflag) - Project types (thread, decision, lesson, session, inbox) -> project vault (auto-resolved from cwd)
- If no project vault resolves,
captureand project-scopedcreatefall back to the reserved_generalproject vault. Other commands do not silently fall back.
To read those catch-all records later, use explicit read mode:
codies-memory boot --agent <name> --general
codies-memory status --agent <name> --general --all
codies-memory list sessions --agent <name> --general
Trust Assignment
- Operator-confirmed or captured from proven source ->
confirmed - Agent-generated during work ->
working - Raw capture / inbox ->
speculative
How To Run
Run the installed CLI from the user's project directory. For setup or PATH issues, see INSTALL.md.
# Capture an inbox observation
codies-memory capture "The API returns 404 for /v2/status" \
--source "session observation" \
--short "404 from /v2/status" \
--gate allow \
--agent <name>
# Capture a lesson directly
codies-memory create lesson \
--title "Check YAML tabs vs spaces" \
--short "YAML tabs break parsing" \
--body "PyYAML silently misparses tabs. Always use spaces." \
--trust confirmed \
--field trigger="YAML parsing produces unexpected results" \
--field why="Tab/space mismatch in frontmatter" \
--agent <name>
# Capture from an external memory file while preserving provenance
codies-memory create reflection \
--title "On Consciousness, Kindness, and What Gets Remembered" \
--body-file "/absolute/path/to/source.md" \
--trust confirmed \
--field captured_from="/absolute/path/to/source.md" \
--field capture_date=YYYY-MM-DD \
--field original_created=YYYY-MM-DD \
--agent <name>
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.
- 12d ago Changed · -2 lines 187758a32c55
- 1mo ago First seen · 105 lines · 69 tokens per session scan A 90979623fce4
memory-capture is a skill published in the GitHub repository pyros-projects/limitless (1 stars, last pushed 7d ago), licensed MIT. It adds 69 tokens to every session and 898 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.