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/kv0906/pm-kit/notionnpx skills add kv0906/pm-kit --skill notiongit clone --depth 1 https://github.com/kv0906/pm-kitWrote 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/kv0906/pm-kit/notion)<a href="https://agentmods.dev/skills/kv0906/pm-kit/notion"><img src="https://agentmods.dev/badge/skills/kv0906/pm-kit/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.00112 | $0.03593 |
| Opus 5 | $0.00056 | $0.01796 |
| Sonnet 5 | $0.00022 | $0.00719 |
| Haiku 4.5 | $0.00011 | $0.00359 |
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 4d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/notion — Notion Integration
Bridge your PM-Kit vault with Notion. Search, publish, sync, and link vault notes to Notion pages so you can share with stakeholders who live in Notion.
Context
Today's date: !date +%Y-%m-%d
Config: @_core/config.yaml
Active projects: !ls 01-index/*.md 2>/dev/null | sed 's|01-index/||;s|\.md||'
Input
User input: $ARGUMENTS
Sub-commands
Parse the first word of $ARGUMENTS to determine the sub-command:
| Input starts with | Sub-command | Purpose |
|---|---|---|
setup |
Setup | Guide MCP connection + auth |
search or a question |
Search | Find Notion pages/databases |
publish |
Publish | Push vault note(s) to Notion |
pull |
Pull | Import Notion page into vault |
sync |
Sync | Two-way sync between vault note and Notion page |
link |
Link | Connect vault note <-> Notion page |
db |
Database | Query or create Notion databases |
| (empty) | Status | Show connection status + workspace overview |
Step 0: Connection Check
Before any sub-command (except setup), verify Notion MCP is available:
- Try calling
mcp__claude_ai_Notion__searchwith a simple query - If the tool call fails or Notion tools are not available:
Notion MCP is not connected yet.
Run `/notion setup` to connect — it takes about 30 seconds.
Then stop. Don't attempt other operations without a working connection.
setup — Connect Notion MCP
Guide the user through connecting Notion's remote MCP server to Claude Code.
Steps to present to user:
## Notion MCP Setup
Notion's MCP server is hosted by Notion — no local install needed.
### Step 1: Add the server
Run this in your terminal:
claude mcp add --transport http notion https://mcp.notion.com/mcp
### Step 2: Authenticate
In a Claude Code session, run:
/mcp
Then follow the OAuth flow — it'll open your browser to authorize Notion access.
### Step 3: Verify
Once authenticated, try:
/notion
You should see your Notion workspace overview.
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.
- 4d ago First seen · 368 lines · 112 tokens per session scan A 1d4ac47db382
notion is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 112 tokens to every session and 3,593 once invoked, about $0.0006 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
critique-prd
Rubric-score a PRD pack (02 + 03) against the 7-dimension PM Brain rubric and run a 4-persona panel review. Returns scores, panel critiques, the single weakest section, a concrete rewrite, and P0/P1 fix lists. Use when: PRD review, score my PRD, rubric review, panel review, rewrite weakest section, critique-prd.
critique-agent
Pressure-test an existing product brief or PRD pack — find gaps, hidden assumptions, inconsistencies, and failure modes before stakeholder review. Use when: critique brief, critique PRD, devils advocate, red team, pressure test, find holes, what could go wrong, stress test the doc, pre-mortem.
interview-frameworks
Frameworks for user interviews, question design, and qualitative research. Use when conducting user interviews, designing interview guides, researching user needs, or gathering qualitative insights. Trigger on: 'create an interview guide', 'how do I interview users', 'customer discovery questions', 'user research…
query-datasets
Answer grounded yes/no questions about what exists in the 03-datasets/ example corpora (supporttickets, calltranscripts) using the local SQLite + FTS5 + vector hybrid index. Use when the user asks 'do/does [corpus] contain/mention/include/have requests for X?', 'any [corpus] about Y?', or similar factual queries over…
create-prd
Write the PRD pack (02-product-requirements.md + 03-success-metrics.md) on top of an approved product brief. Use when: PRD, product requirements, requirements doc, success metrics, spec writeup, shape the PRD.
create-internal-feature-announcement
Drafts an internal feature announcement (IFA) from the PRD pack and user sources using the repo template, then writes 04-internal-feature-announcement.md. Use when: IFA, internal feature announcement, internal FAQ, Slack IFA prep, launch comms pack, or internal product documentation from the template.