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/aiyo28/memento-os/session-completenpx skills add Aiyo28/memento-os --skill session-completegit clone --depth 1 https://github.com/Aiyo28/memento-osWrote 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/aiyo28/memento-os/session-complete)<a href="https://agentmods.dev/skills/aiyo28/memento-os/session-complete"><img src="https://agentmods.dev/badge/skills/aiyo28/memento-os/session-complete.svg" alt="Measured on agentmods" 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.00077 | $0.01455 |
| Opus 5 | $0.00039 | $0.00727 |
| Sonnet 5 | $0.00015 | $0.00291 |
| Haiku 4.5 | $0.00008 | $0.00145 |
Grade A, and why
session-complete 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 6d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/session-complete
Extract what matters. Discard the rest. Update continuity docs.
Mode Detection
| Signal | Mode | Behavior |
|---|---|---|
| End of session | default |
Full extraction + NEXT.md + session log |
| Before compaction | --compact |
Quick extraction + NEXT.md only (speed matters) |
Steps
1. Scan Conversation for Reasoning Artifacts
Extract:
- Decisions made →
[D]artifacts - Insights learned →
[I]artifacts - Errors resolved →
[E]artifacts with root cause - Ideas deferred with conditions →
[S]seeds (forward-looking ideas that surface when a condition is met)
For each, draft the inline format:
`[D] <conclusion> — invalidates if <trigger> [priority] [YYYY-MM-DD]`
`[I] <insight> — invalidates if <condition> [priority] [YYYY-MM-DD]`
`[E] <what went wrong> — root cause: <why> — fix: <what solved it> [settled] [YYYY-MM-DD]`
`[S] <idea> — activates when <condition> [priority] [YYYY-MM-DD]`
Optional expiry: If the conclusion is time-bound (free tier, trial, beta, seasonal, "for now"), add — expires: YYYY-MM-DD before priority. Do NOT add expiry to foundational architecture decisions.
Seeds are ideas that came up but weren't actionable yet. Look for "maybe later", "when we have X", "not now but eventually".
Where [priority] is derived from:
- Claude proposes confidence (high/medium/low)
- Ask user: "High or low impact?"
- Matrix: high confidence + high impact = critical, low + low = noise, etc.
[E]errors default to settled; once resolved → noise- In
--compactmode: skip impact prompt — default all tosettled
2. Contradiction Check
Before confirming, scan existing artifacts in _context.md for contradictions with new ones:
- For each new
[D]or[I], grep the Active Reasoning Artifacts table for overlapping topics - If a new artifact supersedes an existing one (same domain, updated conclusion):
- Mark the old artifact for eviction to
Decisions/withstatus: superseded - Show:
"#X superseded: <old> → <new>"
- Mark the old artifact for eviction to
- If a new artifact contradicts an existing one (conflicting conclusions, both may be valid):
- Flag:
"Conflict: new <artifact> vs existing #X — keep both, or resolve?"
- Flag:
- If no overlap → proceed normally
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.
- 6d ago First seen · 136 lines · 77 tokens per session scan A 4ff8ecc38b98
session-complete is a skill published in the GitHub repository Aiyo28/memento-os (3 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 1,455 once invoked, about $0.0004 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…