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 agentmods add skills/imoonkey/openweb/notionnpx skills add imoonkey/openweb --skill notiongit clone --depth 1 https://github.com/imoonkey/openwebWhat 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 | $0.00000 | $0.01116 |
| Opus 5 | $0.00000 | $0.00558 |
| Sonnet 5 | $0.00000 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00112 |
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 2d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion
Overview
Productivity and collaboration workspace. Enterprise archetype.
Workflows
Search pages
getSpaces→ pick workspace →spaceIdsearchPages(query, spaceId)→ results with pageid,title,score
Read a page
searchPages(query, spaceId)→ find pageidin resultsgetPage(pageId)→ blocks inrecordMap.block, properties in root block'svalue.properties
Query a database
searchPages(query, spaceId)→ findcollection_view_pageblocks inrecordMap.block→collection_id,view_idsqueryDatabase(collectionId, viewId)→ rows with property values
Note: collection_id is found in blocks of type collection_view_page within search results' recordMap.block. It may not appear in system databases ("Home views", "My Tasks") — only user-created databases.
Create a page
getSpaces→spaceIdcreatePage(title, spaceId)→ newpageId- Optionally pass
parentIdto nest under an existing page
- Optionally pass
Update a page
searchPages(query, spaceId)→ find page →pageIdupdatePage(pageId, title, spaceId)→ updated page info
Delete a page
searchPages(query, spaceId)→ find page →pageIddeletePage(pageId, spaceId)→deleted: true- Moves page to trash — recoverable from Notion UI
- Reverse of
createPage
Operations
| Operation | Intent | Key Input | Key Output | Notes |
|---|---|---|---|---|
| getSpaces | list workspaces | — | userId, spaceId | entry point for spaceId |
| searchPages | full-text search | query, spaceId | results[].id, score, recordMap | paginated via limit |
| getPage | read page content | pageId | recordMap.block (page tree), cursor | paginated via chunkNumber |
| queryDatabase | filter/sort database rows | collectionId, viewId | blockIds, recordMap.block (rows) | needs collectionId from search |
| createPage | create page | title, spaceId, parentId? | pageId | write op — adapter-based |
| deletePage | delete (trash) page | pageId, spaceId | deleted: true | write op — reverse of createPage |
| updatePage | update page title | pageId, title, spaceId | updated: true | write op — adapter-based |
What ships with it
12 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.
- adapters/notion-api.ts 6.1 KB runs code
- DOC.md 6.2 KB
- examples/createPage.example.json 360 B
- examples/deletePage.example.json 371 B
- examples/getPage.example.json 517 B
- examples/getSpaces.example.json 226 B
- examples/queryDatabase.example.json 777 B
- examples/searchPages.example.json 1.1 KB
- examples/updatePage.example.json 409 B
- manifest.json 203 B
- openapi.yaml 26 KB
- PROGRESS.md 2.8 KB
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.
- 2d ago First seen · 84 lines · 0 tokens per session scan A 402af06b6736
notion is a skill published in the GitHub repository imoonkey/openweb (58 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,116 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…