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/lanterncx/agent/record-memorynpx skills add LanternCX/Agent --skill record-memorygit clone --depth 1 https://github.com/LanternCX/AgentWhat 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.00023 | $0.00529 |
| Opus 5 | $0.00012 | $0.00264 |
| Sonnet 5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
record-memory 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Record Memory
Overview
Record durable project memory for a completed change unit.
Entry Conditions
Create a memory entry only when all of the following are true:
- The work has one clear goal.
- The work forms one coherent, reviewable change unit.
- The work is complete enough to preserve as durable project memory.
Do not use memory entries as work logs for exploration, partial work, or scattered trivial changes.
Discovery Order
Every entry belongs to exactly one type.
If discovery cannot identify one unique type, stop and ask the user to clarify.
Discover the target type in this order:
- Scan
docs/superpowers/memory/*/MEMORY.md. - Read each candidate header's
Type,Record When,Avoid Recording When, andEntry Template. - Choose the best-matching type for the completed change unit.
- After selecting the type, read only that type's
ENTRY.mdbefore writing. - Write the entry under
docs/superpowers/memory/<type>/entries/<YYYY-MM>/. - Update only that type's
INDEX.mdatdocs/superpowers/memory/<type>/INDEX.md.
Do not hardcode type names or type meaning from this skill alone. Repository memory files are the source of truth.
This skill only routes recording work. It never retrieves, summarizes, or pre-reads historical memory for the current task.
If the task first needs project history to reduce uncertainty, hand off to using-memory; Use When / Avoid When are retrieval-facing fields and are not recording fallbacks.
Stop Conditions
Stop and ask the user to clarify when:
- multiple discovered types fit and no clear choice exists
- no discovered type fits and a new type may be needed
- the completed work cannot be reduced to one reviewable change unit
Bootstrap Handoff
Read bootstrap.md, restore only the minimum missing structure, then restart discovery when:
docs/superpowers/memory/is missing- scanning finds no usable
docs/superpowers/memory/*/MEMORY.md - a scanned
MEMORY.mdis missing required record-facing fields, or cannot be parsed; treat that type as structurally damaged - the selected type is missing
ENTRY.md - the selected type is missing
INDEX.md - the selected type is missing its target month bucket under
entries/<YYYY-MM>/
What ships with it
13 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.
- bootstrap.md 5.2 KB
- template/type/base/ENTRY.md 502 B
- template/type/base/INDEX.md 105 B
- template/type/base/MEMORY.md 424 B
- template/type/debug/ENTRY.md 549 B
- template/type/debug/INDEX.md 105 B
- template/type/debug/MEMORY.md 826 B
- template/type/milestone/ENTRY.md 535 B
- template/type/milestone/INDEX.md 105 B
- template/type/milestone/MEMORY.md 1.0 KB
- template/type/refactor/ENTRY.md 532 B
- template/type/refactor/INDEX.md 105 B
- template/type/refactor/MEMORY.md 904 B
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 First seen · 59 lines · 23 tokens per session scan A a3622ba70411
record-memory is a skill published in the GitHub repository LanternCX/Agent (5 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 529 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…