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 makenotion/notion-cookbook --skill calendargit clone --depth 1 https://github.com/makenotion/notion-cookbookWrote 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/makenotion/notion-cookbook/calendar)<a href="https://agentmods.dev/skills/makenotion/notion-cookbook/calendar"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/calendar/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/makenotion/notion-cookbook/calendar"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/calendar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 33 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00032 | $0.01328 |
| Opus 5 | $0.00016 | $0.00664 |
| Sonnet 5 | $0.00006 | $0.00266 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
calendar scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(new URL("/v1/tools/run", baseUrl), { How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calendar workflows
Use an authorized calendar connection and fetch calls to the Notion tools
API. This is an Apps alpha feature, not direct access to Google Calendar or
Microsoft Graph. Read the tool reference before choosing
an operation or writing its request body. It covers all 13 calendar tools.
Connection and access
Import connections from @notionhq/apps/workflow and add
connections: [connections.calendar()] to the workflow. The declaration asks
for a connection; it does not grant access. Finish calendar setup for the
installed workflow, select its calendars and default calendar, and publish its
configuration before running it. Use only the tools and calendars authorized
for that connection.
Use the runtime's NOTION_API_TOKEN and NOTION_API_BASE_URL (default:
https://api.notion.com). Never hard-code or log a token. Local checks do not
need credentials. Live execution needs an eligible workflow token and a ready
connection; a normal integration token or a personal agent's calendar access
does not replace that setup.
If access is denied, check Apps calendar availability, published workflow setup, enabled tools, connection health, and calendar permissions. A workflow cannot pause for calendar write confirmation: writes that require confirmation are denied. Ask the owner to choose suitable permissions for the intended work; do not bypass confirmation or broaden access in code.
Request pattern
POST to /v1/tools/run with Notion-Version: 2026-03-11. The type and the
sibling payload key must both be the exact snake_case tool name. Keep the
payload's camelCase field names. Send only that tool's inputs, not Calendar
service config, params, account credentials, or permission overrides.
This example lists the next 24 hours, not a local calendar day or week. Adapt the trigger and time zone to the requested job.
import { triggers } from "@notionhq/apps/triggers"
import { connections, createWorkflow } from "@notionhq/apps/workflow"
export default createWorkflow({
name: "List upcoming calendar events",
description: "Lists events in the next 24 hours.",
triggers: [triggers.notionPageCreated()],
connections: [connections.calendar()],
handler: async (_event, context) => {
const range = await context.step("Choose time range", () => {
const now = Date.now()
return {
timeMin: new Date(now).toISOString(),
timeMax: new Date(now + 24 * 60 * 60 * 1000).toISOString(),
timeZone: "America/New_York",
}
})
await context.step("List calendar events", async () => {
const token = process.env.NOTION_API_TOKEN
if (!token) throw new Error("NOTION_API_TOKEN is required.")
const baseUrl =
process.env.NOTION_API_BASE_URL || "https://api.notion.com"
const response = await fetch(new URL("/v1/tools/run", baseUrl), {
method: "POST",
headers: {
Authorization: `Bearer ${token}`,
"Content-Type": "application/json",
"Notion-Version": "2026-03-11",
},
body: JSON.stringify({
type: "calendar_list_events",
calendar_list_events: range,
}),
})
if (!response.ok) {
throw new Error(`Calendar lookup failed (HTTP ${response.status}).`)
}
const result: unknown = await response.json()
if (
!result ||
typeof result !== "object" ||
("object" in result && result.object === "error") ||
!("accounts" in result) ||
!Array.isArray(result.accounts) ||
!("errors" in result) ||
!Array.isArray(result.errors)
) {
throw new Error("Invalid calendar lookup response.")
}
if (result.errors.length > 0) {
throw new Error(
`Calendar lookup failed for ${result.errors.length} calendars.`
)
}
return result
})
},
})
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.
- 6d ago First seen · 137 lines · 32 tokens per session scan A 7be3b2f17c48
calendar is a skill published in the GitHub repository makenotion/notion-cookbook (206 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,328 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
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…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.