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 ericrisco/rsc-harness --skill notion-connectorgit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/notion-connector)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/notion-connector"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/notion-connector/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/ericrisco/rsc-harness/notion-connector"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/notion-connector.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.00086 | $0.02701 |
| Opus 5 | $0.00043 | $0.01350 |
| Sonnet 5 | $0.00017 | $0.00540 |
| Haiku 4.5 | $0.00009 | $0.00270 |
Grade A, and why
notion-connector 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 7d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion connector — Notion as a code-backed ops store
Wire server code to the Notion HTTP API so a database behaves like a small operational store: push rows, pull rows, sync both ways idempotently, read and write page blocks. This skill owns the outbound Notion API surface only — the database/data-source data model, property-type write shapes, and the rate-limit/pagination discipline that the API forces on you.
Route elsewhere
| Situation | Route to |
|---|---|
| Generic "call any REST API", nothing Notion-specific | ../api-connector-builder/SKILL.md |
| Receiving + verifying inbound Notion webhook events | ../webhooks/SKILL.md |
| Notion is one node in a multi-tool sequence | ../automation-flows/SKILL.md |
| CSV/tabular bulk transforms, column mechanics | ../spreadsheet-ops/SKILL.md |
| Token handling, secret rotation, never-client-side rules | ../secure-coding/SKILL.md |
Setup (4 steps)
- Create an internal integration in Notion → Settings → Integrations. Copy
the secret — it looks like
ntn_...(older onessecret_...). - Put the token in an env var, never in client-side JS, never committed. It
is a bearer secret; treat it like a password. See
../secure-coding/SKILL.md. - Share the target database/page with the integration in the Notion UI
(the page
•••menu → Connections). Skip this and every call 404s or returns empty — the integration sees nothing it was not explicitly granted. - Construct the SDK client with a pinned
Notion-Version. Official JS SDK is@notionhq/clientv5.12.0+ (latest 5.22.0, 2026-05-19); its defaultnotionVersionis the current major2025-09-03, and it supports the latest2026-03-11if you opt in. The default and method names below are stable across the whole 5.x line. Behavior differs across versions, so pin it per client (or per request) — an unpinned client drifts when the default moves.
import { Client } from "@notionhq/client"; // v5.12.0+ (latest 5.22.0)
const notion = new Client({
auth: process.env.NOTION_TOKEN, // ntn_... — env only, never inlined
notionVersion: "2025-09-03", // pin it; do not ride the default
});
What ships with it
6 files 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.
- 7d ago First seen · 222 lines · 86 tokens per session scan A 55c9ec8f2ce8
notion-connector is a skill published in the GitHub repository ericrisco/rsc-harness (78 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 2,701 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
dev-supabase
Backend development with Supabase. Trigger when the user wants to configure auth, the database, or Supabase storage.
traverse-multi-hop
Expresses a multi-hop lineage question as a single variable-length path match against native graph storage, bounded by an explicit hop depth and an explicit relationship-type allowlist, instead of a recursive relational join that grows one level per hop.
transact-graph-write
Wraps every write to a shared graph edge in a transaction tied to the exact row version it was computed against, and retries a rejected write against the row's current state instead of dropping it or blindly reapplying stale values.
attach-receipts
Attaches sourcedoc/extractionrunid/schemaversion receipts to every edge at write time, and refuses to write any edge missing one of the three.
query-graph
Loads schema.sql into a local SQLite file, then answers availability and provenance questions against the nodes/edges tables with real SQL instead of re-reading source material.
score-and-merge
Scores candidate merge pairs on weighted signals and auto-merges only pairs clearing a stated threshold, routing the rest to a review queue with their score and signal breakdown attached.