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/djrhails/dotfiles/notionnpx skills add DJRHails/dotfiles --skill notiongit clone --depth 1 https://github.com/DJRHails/dotfilesWrote 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/djrhails/dotfiles/notion)<a href="https://agentmods.dev/skills/djrhails/dotfiles/notion"><img src="https://agentmods.dev/badge/skills/djrhails/dotfiles/notion.svg" alt="Measured on agentmods" 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 | $0.00076 | $0.01007 |
| Opus 5 | $0.00038 | $0.00504 |
| Sonnet 5 | $0.00015 | $0.00201 |
| Haiku 4.5 | $0.00008 | $0.00101 |
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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion CLI
Read Notion via the unofficial /api/v3 endpoint using token_v2 from the user's browser (Arc by default). Sees every page their logged-in browser sees — including pages shared by guests from other workspaces, which the official API can't reach without per-page integration grants.
Prerequisites
- User signed into Notion web in a Chromium-family browser (Arc, Chrome, Chromium, Brave, Edge, Firefox, Safari)
uvinstalled — the script is PEP 723 souv runself-resolves dependencies (browser-cookie3,diskcache,emboss,pydantic,requests,rich,typer)
Commands
All commands use notion.py from this skill dir. Default browser is Arc; override with -b chrome|brave|edge|firefox|safari|chromium.
Fetch a page as Markdown
./notion.py get <page-id-or-url> # → stdout
./notion.py get <page-id-or-url> -o out.md # → file
./notion.py get <page-id-or-url> --raw # raw recordMap JSON instead of rendered Markdown
<page-id-or-url> accepts:
- Full Notion URL:
https://www.notion.so/Page-Title-292ff732fc3480d0a39ee6a78db70f82 - 32-hex slug tail:
292ff732fc3480d0a39ee6a78db70f82 - Dashed UUID:
292ff732-fc34-80d0-a39e-e6a78db70f82
Renders headings, paragraphs, bullets, numbered lists, code (language preserved), quotes, callouts, dividers, bookmarks, images, to-dos, toggles. Empty language=markdown code blocks (a Notion authoring quirk) are unwrapped.
List logged-in identities
./notion.py whoami
Enumerates each browser profile with a token_v2 cookie and prints the user + workspaces. Useful for figuring out which Arc profile has a particular workspace.
Search a workspace
./notion.py search "<query>" --space <space-id>
./notion.py search "<query>" --from-page <page-id> # resolve space from a page you can access
Slack-style workspace search. --from-page is the easier path when you don't know the space ID off-hand.
Auth
Browser cookies do everything — no env vars, no tokens to manage. If a profile has Notion cookies, that profile's identity is used. With multiple profiles signed into different Notion accounts, the script uses cookies from the profile that can resolve the page.
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.
- 3d ago First seen · 81 lines · 76 tokens per session scan A 256ecc133bbb
notion is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,007 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-08-31.
Other skills, from other repositories
walkthrough
Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.
prd-view
Render a PRD Markdown file as a rich, self-contained HTML reading view (Dashboard style) and open it in the browser. The Markdown stays authoritative; the HTML is a derived, ephemeral presentation.
autopilot-batch
Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot at the build model from its 'model:' label — with a gating review at Opus 5 or above and never below the build (Opus reviews Sonnet and Opus builds, Fable reviews Fable builds).
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
qa-handoff
Generate a hands-on QA testing guide as a self-contained HTML page — for Rails apps or static (Hugo) sites. --publish uploads the HTML to the project's configured QA host.