Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rjmurillo/ai-agentsnpx agentmods add skills/rjmurillo/ai-agents/memory-reflexionWrote 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/rjmurillo/ai-agents/memory-reflexion)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/memory-reflexion"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/memory-reflexion.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00098 | $0.01813 |
| Opus 5 | $0.00049 | $0.00907 |
| Sonnet 5 | $0.00020 | $0.00363 |
| Haiku 4.5 | $0.00010 | $0.00181 |
Grade A, and why
memory-reflexion 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Reflexion
Tier 2 episodic write operations: the reflexion write path extracted from the
memory router per ADR-063 (memory-skill decomposition). memory still routes
here; a caller that needs only to record a session outcome loads this sub-skill
instead of the full memory surface.
Reflexion is one operation: extract an episode from a completed session log. The episode record is the durable artifact. It is committed to the repository and read directly by downstream consumers.
[!NOTE] This sub-skill previously carried a second step that folded episodes into a derived causal graph (Tier 3). ADR-089 removed that layer: nothing read it, and its aggregated output was noise. Episodes are unaffected and remain the system of record. See ADR-089 for the evidence.
Triggers
Use this skill when the user says:
extract episode from sessionto capture a completed session as an episoderecord what happened this sessionfor the reflexion write pathre-extract this episodeto refresh a record over an existing episode file
Quick Start
# Extract an episode from a completed session log (Tier 2)
python3 .claude/skills/memory/scripts/extract_session_episode.py "<session-log-path>"
# Re-extract over an existing episode, merging rather than clobbering
python3 .claude/skills/memory/scripts/extract_session_episode.py "<session-log-path>" --preserve
The script is canonical and shared with the memory router; this sub-skill does
not reimplement it. It lives at
.claude/skills/memory/scripts/extract_session_episode.py.
Quick Reference
| Operation | Script | Key Parameters |
|---|---|---|
| Extract episode (Tier 2) | extract_session_episode.py |
session_log_path, --output-path, --force, --preserve |
--force and --preserve are mutually exclusive. --force overwrites an
existing episode file. --preserve merges a fresh extraction over the existing
record without dropping richer data already there.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 9e89ccb6c526
- 4d ago First seen · 190 lines · 98 tokens per session scan A 8d4af81f727f
memory-reflexion is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 1,813 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
context-recovery
Recover missing conversation context after explicit compaction or truncation, or when the user explicitly asks to recover prior work. Use for requests such as "where were we before compaction?" when the current thread is insufficient. Do not trigger on a generic "continue" when the current thread already provides an…
ci-cd
A guide for designing automated build and delivery workflows with GitHub Actions. These workflows can run checks such as tests, code-quality scans, coverage checks, and builds when code is pushed or a pull request is opened.
context-search
A continuity workflow for finding context from earlier coding-agent sessions. It can inspect continuation notes and session records when a task refers to previous work.
abmind-runtime-operations
Inspect and maintain abmind memory, persona files, sleep, backups, encryption, and runtime health.
memory-search
Search persistent memory for facts, decisions, and past conversations.
topic-save
Save and manage topic-specific knowledge files from conversations.