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 zackbart/connecta --skill notiongit clone --depth 1 https://github.com/zackbart/connectaWrote 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/zackbart/connecta/notion)<a href="https://agentmods.dev/skills/zackbart/connecta/notion"><img src="https://agentmods.dev/badge/skills/zackbart/connecta/notion/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/zackbart/connecta/notion"><img src="https://agentmods.dev/badge/skills/zackbart/connecta/notion.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.00002 | $0.02870 |
| Opus 5.5 | $0.00001 | $0.01148 |
| Sonnet 5.5 | $0.00000 | $0.00574 |
| Haiku 4.5 | $0.00000 | $0.00287 |
Grade A, and why
notion 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 yesterday.
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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion MCP usage
Official MCP interface: tool names, descriptions, argument schemas, and result schemas come from Notion's live server. Connecta preserves that catalog and applies release-reviewed classification. Reviewed writes stay writes even when Notion claims they only read.
Workspace purpose:
- This connection acts as its OAuth-authorized user and reaches what that user
can. It holds no integration token. An internal integration (bot) is a
separate connector with
auth: { type: "token" }under another id; never switch to it to recover a failed call here. - Discover the live catalog before assuming a tool exists. Notion can gate
tools by workspace, account, client, and rollout independently of Connecta.
notion-get-tool-accessreports what the workspace's plan allows. - Start broad discovery with
notion-search, then usenotion-fetchon the exact page, database, data source, or object before changing it. - Use the live input schema as the contract. Notion owns these MCP schemas; the REST schemas of Connecta's token connector do not apply to MCP tools with similar names.
- Session and agent tools can launch asynchronous work. Read session state and events before sending another message, waiting, or stopping a session.
- File uploads and attachment tools create durable workspace state. Keep
downloads inside the requested task and do not expose signed attachment URLs.
notion-download-skillreturns a signed, expiring archive URL by design; the token connector's REST redaction does not apply to hosted tools, so use that URL for the download and do not repeat it in replies. - Connecta's generic REST tools (
notion_api_*) and theintegration_*helpers exist only on a token connector. - An
auth_requiredfailure means this connector's OAuth grant is missing or expired. Runauthorize_connectorfor this connector id, then retry.
What ships with it
11 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.
- drift.json 3.6 KB
- fixtures.ts 768 B runs code
- index.ts 14 KB runs code
- openapi.generated.ts 105 KB runs code
- openapi.source.json 374 B
- provider.test.ts 62 KB runs code
- rest.ts 55 KB runs code
- skill.generated.ts 13 KB runs code
- value-safety.candidates.json 1.8 KB
- value-safety.node.test.ts 1.3 KB runs code
- value-safety.ts 2.3 KB runs code
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.
- yesterday Changed · +36 lines 9fce3abe341e
- 5d ago Changed · +32 lines bbf0e0050d87
- 6d ago First seen · 147 lines · 2 tokens per session scan A b3b24d1c6afb
notion is a skill published in the GitHub repository zackbart/connecta (0 stars, last pushed today), licensed MIT. It adds 2 tokens to every session and 2,870 once invoked, about $0.0000 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-10-08.
Other skills, from other repositories
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…