Borrowing it
Nothing to install: this file belongs to catfish-1234/sessionmem. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/catfish-1234/sessionmem/main/AGENTS.mdgit clone --depth 1 https://github.com/catfish-1234/sessionmemWrote 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/instructions/catfish-1234/sessionmem/agents-md)<a href="https://agentmods.dev/instructions/catfish-1234/sessionmem/agents-md"><img src="https://agentmods.dev/badge/instructions/catfish-1234/sessionmem/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/catfish-1234/sessionmem/agents-md"><img src="https://agentmods.dev/badge/instructions/catfish-1234/sessionmem/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00870 | $0.00870 |
| Opus 5.5 | $0.00348 | $0.00348 |
| Sonnet 5.5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
sessionmem AGENTS.md 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sessionmem: Persistent Memory
sessionmem is an MCP memory layer that persists context across sessions. It is installed and active via the sessionmem MCP server. Use its tools to recall prior context and to store important decisions, facts, and context so they're available in future sessions. The user should never have to ask you to do this. It is part of how you work in this project.
Startup
On Claude Code, prior context is injected automatically at session start by the
sessionmem SessionStart hook. You do not need to fetch it yourself. Do NOT
call startup_inject_memories on Claude Code: the hook already provides the
injection, so calling the tool would duplicate the context (it is not even
registered on Claude Code for this reason). If you do NOT see a "Relevant prior
context" block at the start of the session AND the startup_inject_memories
tool is available (e.g. the hook is not installed, or you are on a host without
hook support), call it once before any task work, or call retrieveMemories
with the current task as the query. Never inject twice if context was already
provided.
When to store memories (storeMemory)
- User makes an architectural or design decision
- You discover a non-obvious project constraint or convention
- A debugging session reveals an important root cause
- User states a preference about how they want things done
- A warning or pitfall is discovered that future sessions should know about
When to retrieve memories mid-session (retrieveMemories)
- Before making architectural decisions (check if prior decisions exist)
- When the user references something from a previous session
- When working in an area of the codebase that may have stored warnings or decisions
At session end (RECOMMENDED: do this without being asked)
Before the session ends, persist what was accomplished so the next session starts
informed. Store a concise summary memory (importance 7) of the key outcomes, plus
any new decisions, facts, or warnings. Use batchStoreMemory to write several at
once. This is what makes context survive across sessions and saves tokens later.
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.
- 1mo ago First seen · 73 lines · 870 tokens per session scan A 566decc8c4dc
sessionmem AGENTS.md is an instructions file published in the GitHub repository catfish-1234/sessionmem (9 stars, last pushed 2d ago), licensed MIT. It adds 870 tokens to every session, about $0.0035 per session on Opus 5.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 instructions, from other repositories
data-scientist copilot-instructions.md
Repository instructions for a data-science workflow in GitHub Copilot, covering datasets, statistics, and analysis files.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).