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/soden46/engineer-flow/memory-managementnpx skills add soden46/engineer-flow --skill memory-managementgit clone --depth 1 https://github.com/soden46/engineer-flowWrote 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/soden46/engineer-flow/memory-management)<a href="https://agentmods.dev/skills/soden46/engineer-flow/memory-management"><img src="https://agentmods.dev/badge/skills/soden46/engineer-flow/memory-management.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 | $0.00038 | $0.00279 |
| Opus 5 | $0.00019 | $0.00139 |
| Sonnet 5 | $0.00008 | $0.00056 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
memory-management 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 3d 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.
What it actually says
Memory Management
Use memory as conditional infrastructure, not specialist expertise.
Preflight
Run memory preflight only when prior project/session/workflow context could materially affect correctness. Skip self-contained tasks.
Prefer an active MCP memory tool when the host provides one. Otherwise use:
node skills/engineer-flow/infrastructure/memory-management/scripts/memory.mjs auto --cwd <project-root> --query "<task intent>" --limit 5
The command prints decision: RUN or decision: SKIP. On RUN, use only sparse relevant memory and verify it against current code/config.
Rules
- Memory never consumes primary or support specialist slots.
- Current code/config beats old memory.
- Do not store secrets,
.envvalues, raw credentials, or personal data. - Preserve provenance and status.
- Checkpoint only durable reusable knowledge.
Checkpoint
After meaningful work, checkpoint only when durable knowledge changed:
node skills/engineer-flow/infrastructure/memory-management/scripts/memory.mjs checkpoint --project <alias> --summary "<durable summary>"
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.
- 3d ago First seen · 39 lines · 38 tokens per session scan A 215139dd2045
memory-management is a skill published in the GitHub repository soden46/engineer-flow (3 stars, last pushed 6d ago), licensed MIT. It adds 38 tokens to every session and 279 once invoked, about $0.0002 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
llm-wiki
Build and maintain an LLM-curated personal knowledge base — the "LLM Wiki" pattern from Andrej Karpathy's April 2026 gist. Use this skill whenever the user wants to ingest a source (paper, article, transcript, PDF, notes) into a persistent compounding knowledge base, ask a question against accumulated notes, lint or…
kb-answer
Answer questions using your project's knowledge base with evidence-backed citations. Every answer must cite literal quotes from KB files to prevent hallucinations. Use this for any question that should be answered from documented knowledge rather than general knowledge.
kb-import
Import knowledge from existing documents into structured KB entries. Reads source documents (Markdown, PDF, DOCX, plain text), extracts key information, and creates properly formatted KB entries with YAML frontmatter.
kb-refresh
Add new sources to your knowledge base or re-scrape existing ones to pick up changes. Supports Notion, Slack, Confluence, and local files. Can be run anytime after /setup-knowledge-base.
setup-knowledge-base
Interactive onboarding to create a structured knowledge base. Defines categories, scaffolds the directory structure, creates the index, and optionally imports initial content. Run this first before using /kb-answer or /kb-import.
session-search
Find context from past Claude Code (CLI) and Claude Cowork (desktop) sessions on this Mac. Use when the user wants to recall something they did before but can't find it , phrasings like "where did I work on X", "find that session where I…", "when did I last do Y", "pull up the conversation about Z", "that time I…