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 skills add kkauf/claude-notion --skill notion-docsgit clone --depth 1 https://github.com/kkauf/claude-notionWrote 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/kkauf/claude-notion/notion-docs)<a href="https://agentmods.dev/skills/kkauf/claude-notion/notion-docs"><img src="https://agentmods.dev/badge/skills/kkauf/claude-notion/notion-docs/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/skills/kkauf/claude-notion/notion-docs"><img src="https://agentmods.dev/badge/skills/kkauf/claude-notion/notion-docs.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.00063 | $0.02355 |
| Opus 5 | $0.00032 | $0.01177 |
| Sonnet 5 | $0.00013 | $0.00471 |
| Haiku 4.5 | $0.00006 | $0.00235 |
Grade A, and why
notion-docs 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 8d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain — Notion Knowledge Base
Overview
The Knowledge Base is the "brain" of your organization — the semantic layer where strategy, priorities, metrics, and decisions live. The code repo is the "limbs" (execution). Docs in the codebase are "muscle memory" (how the limbs work).
Source of truth for: Active Context, strategy docs, billing, positioning, pricing model, platform strategy.
NOT for: Code docs (live in repo), legal docs (GDrive), spreadsheets, team artifacts.
Architecture
Hierarchical pages under a Brain root page. Five sections act as typed containers:
Brain (root page)
Active Context <- cross-cutting dashboard, stays at root
Konban <- database, managed by konban skill
Strategy/ <- why we build, how we position
Operations/ <- how the business runs day-to-day
Product/ <- what we build, platform specs
Research/ <- external knowledge, read-mostly
Archive/ <- superseded content (hidden from default index)
Pages are found by title regardless of which section they're in. find_page() searches Brain root and all sections automatically.
Metadata callout format (top of each page):
Domain: Strategy | Status: Current | Updated: 2026-02-21
Summary: One-liner description
Page ID: BRAIN_PAGE_ID in your env file (see Credentials below)
Section Routing Table
When creating new pages, route them to the right section:
| Signal | Section | Naming | Icon |
|---|---|---|---|
| Company direction, positioning, "why" | Strategy | Descriptive title | Pick a meaningful emoji |
| Day-to-day execution, billing, playbooks | Operations | Descriptive title | Pick a meaningful emoji |
| Feature specs, platform standards | Product | Descriptive title | Pick a meaningful emoji |
| External research, market/legal analysis | Research | Research: [Topic] prefix |
Pick a meaningful emoji |
| Superseded content | Archive | Keep original name | Keep original icon |
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.
- 8d ago First seen · 253 lines · 63 tokens per session scan A 228be5c65d30
notion-docs is a skill published in the GitHub repository kkauf/claude-notion (2 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 2,355 once invoked, about $0.0003 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.