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/lox/notion-cli/notionnpx skills add lox/notion-cli --skill notiongit clone --depth 1 https://github.com/lox/notion-cliWhat 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.00032 | $0.02172 |
| Opus 5 | $0.00016 | $0.01086 |
| Sonnet 5 | $0.00006 | $0.00434 |
| Haiku 4.5 | $0.00003 | $0.00217 |
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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion CLI
A CLI to manage Notion from the command line, using Notion's remote MCP server.
Prerequisites
The notion-cli command must be available on PATH. To check:
notion-cli version
If not installed:
go install github.com/lox/notion-cli@latest
Or see: https://github.com/lox/notion-cli
Authentication
The CLI uses OAuth authentication for MCP-backed commands. On first use, it opens a browser for authorization:
notion-cli auth login # Authenticate with Notion
notion-cli auth status # Show active profile and OAuth state (diagnostic)
notion-cli auth refresh # Force-refresh; commands auto-refresh on use, so rarely needed
notion-cli auth logout # Clear credentials
For CI/headless environments, set NOTION_ACCESS_TOKEN environment variable.
Some fallback features also use the official Notion API:
notion-cli auth api setup
notion-cli auth api status
notion-cli auth api verify
notion-cli auth api unset
For CI/headless environments, set NOTION_API_TOKEN.
Multiple accounts
Every command accepts --profile <name> (or NOTION_CLI_PROFILE) to target a specific Notion account. Named profiles keep credentials isolated under ~/.config/notion-cli/profiles/<profile>/; the implicit default profile uses the existing top-level paths.
notion-cli auth login --profile work
notion-cli page list --profile work
export NOTION_CLI_PROFILE=work # pin for the shell session
notion-cli auth use work # make work the default profile
Resolution precedence: --profile > NOTION_CLI_PROFILE > notion-cli auth use <name> > implicit default profile.
Available Commands
notion-cli auth # Manage authentication
notion-cli page # Manage pages (list, view, create, upload, edit)
notion-cli db # Manage databases (list, query, create entries)
notion-cli search # Search the workspace
notion-cli comment # Manage comments (list, create)
notion-cli tools # List available MCP tools
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 · 210 lines · 32 tokens per session scan A 0699042ef843
notion is a skill published in the GitHub repository lox/notion-cli (35 stars, last pushed 18d ago), licensed MIT. It adds 32 tokens to every session and 2,172 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
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.