Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. 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/egregore-labs/egregore/main/.claude/skills/notion-connect/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/notion-connect)<a href="https://agentmods.dev/skills/egregore-labs/egregore/notion-connect"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/notion-connect/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/egregore-labs/egregore/notion-connect"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/notion-connect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01051 |
| Opus 5 | $0.00023 | $0.00526 |
| Sonnet 5 | $0.00009 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
notion-connect 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 12d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect the current agent runtime directly to Notion's official hosted MCP.
Arguments: $ARGUMENTS (Optional: status or revoke)
When to invoke
- "connect notion", "set up notion", "link notion" → run the connection flow
- "notion status", "is notion connected" → status
- "disconnect notion", "revoke notion" → revoke
/ingest notionalso enters this flow automatically when the MCP tools are missing. Users do not need to run this skill first.
Product boundary
Notion provides the bridge. Egregore does not register a Notion OAuth app and
does not receive or store the user's Notion OAuth token. The current agent
runtime connects directly to https://mcp.notion.com/mcp; Notion owns the
login and consent screen, and the runtime stores its own authorization.
Say this before opening the login flow:
Notion will connect directly to this agent. Egregore Labs does not receive your Notion login or token. The agent can see what your Notion account can see. Search and fetched content pass through this session; pages you approve are additionally saved as curated shared memory.
Do not claim that the MCP is read-only or limited to selected pages. Notion MCP
uses the signed-in user's permissions. Normal Egregore session capture may
include tool results the agent inspected. The /ingest notion review step is
the boundary for what becomes a curated Notion source in shared memory.
Readiness check
First discover available tools using the runtime's tool registry:
- Claude Code: use ToolSearch with
notion. - Codex/OpenAI clients: search for Notion MCP tools. OpenAI may expose
notion-searchandnotion-fetchassearchandfetch. - Other MCP-aware runtimes: inspect the loaded tools for the Notion server.
The connection is ready when both search and fetch are available. Prefer a
notion-get-self/get-self call for status when present; otherwise a small
search is enough to verify access.
Setup
Use the path for the current runtime. These commands register Notion's official remote MCP only; they do not install an Egregore connector.
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.
- 12d ago First seen · 125 lines · 47 tokens per session scan A ea088162c2ba
notion-connect is a skill published in the GitHub repository egregore-labs/egregore (288 stars, last pushed 8d ago), licensed MIT. It adds 47 tokens to every session and 1,051 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-30.
Other skills, from other repositories
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
xiaohongshu-image-creator
An image-making assistant for Xiaohongshu, a Chinese social platform for lifestyle, product, and educational posts. It creates vertical covers and supporting images matched to the post’s topic, audience, and visual style.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…
docs-framework
This skill should be used when the user asks to "create a review report", "write a status log", "add documentation", "name this artifact", or creates files in the .devflow/docs/ directory. Provides naming conventions, templates, and directory structure for reviews, debug sessions, design docs, and all persistent…