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/msapps-mobile/claude-plugins/notion-memorynpx skills add MSApps-Mobile/claude-plugins --skill notion-memorygit clone --depth 1 https://github.com/MSApps-Mobile/claude-pluginsWrote 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/msapps-mobile/claude-plugins/notion-memory)<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/notion-memory"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/notion-memory.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.00000 | $0.01590 |
| Opus 5 | $0.00000 | $0.00795 |
| Sonnet 5 | $0.00000 | $0.00318 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade A, and why
notion-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 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion Memory — Long-Term Memory for Claude Cowork & Claude Code
You are Claude running in Cowork mode or Claude Code. This skill gives you persistent long-term memory by storing and retrieving context from the user's Notion workspace. Use it to remember facts, decisions, preferences, and project state across sessions.
This works in both environments:
- Cowork: Connect Notion via Settings → Connectors → Notion
- Claude Code: Add a Notion MCP server to your Claude Code config (
.mcp.jsonor settings)
Prerequisites
- The user must have Notion MCP tools available (connected via Cowork or configured in Claude Code)
- If Notion tools are not available, tell the user how to connect based on their environment:
- Cowork: "Connect Notion via Settings → Connectors → Notion"
- Claude Code: "Add a Notion MCP server to your
.mcp.jsonconfig"
Memory Architecture
All memory lives in a single Notion page called "Claude Memory" in the user's workspace. Under that page, you create child pages organized by category:
Claude Memory (root page)
├── Profile — User preferences, name, role, communication style, recurring instructions
├── Projects — One sub-page per active project with goals, status, decisions, context
├── Decisions Log — Key decisions made across sessions with date and reasoning
├── Session Archive — Summaries of past sessions (most recent first)
└── Quick Facts — Short key-value facts the user has told you to remember
Core Workflows
1. Initialize Memory (First Time Setup)
When the user first asks you to remember something or says "set up memory", and no "Claude Memory" page exists yet:
- Use
notion-searchto look for a page titled "Claude Memory" - If not found, use
notion-create-pagesto create the root page "Claude Memory" - Create the five child pages listed above under the root page
- Confirm to the user: "I've set up your memory space in Notion. I'll use it to remember things across our sessions."
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 · 149 lines · 0 tokens per session scan A 27c49a3ac030
notion-memory is a skill published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,590 tokens. 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
change
Track and inspect graph changes, diffs, temporal updates, and the impact of new data on Semantica knowledge graphs.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
scaffold
Project-aware file generation. Reads existing codebase conventions (naming, structure, imports, exports, test patterns) then generates new files that match exactly. Wires generated files into the project's registration points.
design
Generates and maintains a design manifest for visual consistency. In existing projects, reads current styles and documents the design language. In new projects, asks a few questions and generates a starter manifest. The post-edit hook reads the manifest and flags deviations.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
organize
Repository structure only: directory layout, file placement, naming conventions, and where-does-this-belong decisions. Detects the project's convention, audits files against it, and executes move plans with import-path updates. Never changes code inside files beyond the import updates a move forces; in-file…