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/linxule/memex-plugin/memo-writingnpx skills add linxule/memex-plugin --skill memo-writinggit clone --depth 1 https://github.com/linxule/memex-pluginWrote 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/linxule/memex-plugin/memo-writing)<a href="https://agentmods.dev/skills/linxule/memex-plugin/memo-writing"><img src="https://agentmods.dev/badge/skills/linxule/memex-plugin/memo-writing.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.00125 | $0.02277 |
| Opus 5 | $0.00063 | $0.01138 |
| Sonnet 5 | $0.00025 | $0.00455 |
| Haiku 4.5 | $0.00013 | $0.00228 |
Grade A, and why
memo-writing 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 5d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Effective Session Memos
Context
Date: !date +%Y-%m-%d
Project: !basename $(git remote get-url origin 2>/dev/null | sed 's/\.git$//' | xargs basename 2>/dev/null) 2>/dev/null || basename $(pwd)
Topics available for [[wikilinks]]: !ls $(memex path 2>/dev/null)/topics/*.md 2>/dev/null | xargs -I{} basename {} .md | sort | tr '\n' ' ' || echo "(no topics found)"
Core Principle
You were there. A subagent reading the transcript later wasn't. Your memo from full context will always be better than a reconstructed one. Write from experience, not summary.
Capture the journey, not just the destination. Future-Claude needs to understand:
- How things were discovered, not just what was found
- What was tried and failed, not just what worked
- What surprised you or was unexpectedly hard
- Where user and AI disagreed or changed direction
Memo Format
---
type: memo
title: [Specific, searchable title]
project: [project-name] # detected from cwd git root; set explicitly if writing from outside the project
date: [ISO date]
topics:
- topic-name-kebab-case
- another-topic
manual: true # distinguishes manually-written memos from auto-extracted ones
---
# [Title]
## For Future Context
[1-2 sentences: the single most important thing for someone continuing this work]
## Summary
[2-4 sentences: what was the actual work, not "we discussed X" but "we tried Y, discovered Z"]
## What Happened
### Key Decisions
- **[Decision]**: [Why this over alternatives. Note tradeoffs.]
### What Worked / What Didn't
- **Tried**: [Approach that failed or was abandoned] → **Why**: [Reason it failed]
- **Solution**: [What actually worked] → **Insight**: [Why it worked]
### Surprises & Difficulties
- [Unexpectedly hard things, multiple attempts, friction]
- [Surprisingly easy things, or things that solved bigger problems]
### Insights
- [Patterns, gotchas, or principles that transfer to other contexts]
- [Non-obvious discoveries — not "X is complex" but "X fails silently when Y"]
## Perspectives & Tensions
[When user and AI had different takes, or user expressed uncertainty/frustration/changed direction. Preserve quotes when they reveal thinking:]
- **User's priority**: [What the user emphasized or pushed for]
- **AI's approach**: [Where Claude offered alternatives or raised concerns]
- **Resolution**: [How it was decided, or if still open]
[Omit this section entirely if the session was straightforward]
## Open Threads
- [ ] [Concrete next step with enough context to act on]
- [ ] [Unresolved question with why it matters]
- [ ] [Blocked item with what's blocking it]
## Related
- [[existing-topic]]
- [[?suggested-new-concept]]
## Context Signals
- **Difficulty**: [Easy / Moderate / Complex / Grinding]
- **Session character**: [Exploration / Debugging / Implementation / Planning / Discussion]
What ships with it
1 file 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.
- 5d ago First seen · 231 lines · 125 tokens per session scan A 5e0c77a5a265
memo-writing is a skill published in the GitHub repository linxule/memex-plugin (7 stars, last pushed 8d ago), licensed MIT. It adds 125 tokens to every session and 2,277 once invoked, about $0.0006 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
superbrain-distill
Internal SuperBrain skill — run by the detached capture child to distill a session-event delta into routed Obsidian notes. Not for direct user invocation.
superbrain-recall
Search the user's SuperBrain second-brain vault. Use whenever the user references past work, prior decisions, "how did we", "did we already", earlier sessions, a project's history, or anything that may already be recorded — before answering from scratch.
memento
Capture durable knowledge from the current work session into Memento Vault. Use when the user asks to remember, save, capture, or record decisions, discoveries, bug fixes, or reusable patterns.
inception
Run or preview Memento Vault consolidation. Use when the user asks to consolidate, find patterns, run inception, preview clusters, or synthesize cross-session themes.
continue-work
Use when the user says "continue", "pick up where I left off", "what was I working on", or similar. Also use when starting a session and memory has pending work.
concierge
Search Memento Vault for day-to-day recall, past decisions, discoveries, implementation history, and prior session context. Use when the user asks "do you remember", "have we seen", "what did we decide", "what did we learn", "where was this implemented", "find prior context", "check memory", "search the vault", or any…