notion-research-documentation

notion-research-documentation is a skill for Codex from cass-2003/local-workflow-skill. It costs 38 tokens per session (775 once invoked), scanned A, a copy of notion-research-documentation, MIT.

A workflow for researching several Notion pages and combining the findings into structured briefs, comparisons, or reports with source links.

In plain words
What is it for?
Use it to search and read Notion sources, compare information, write summaries or reports, and publish the result back to Notion.
Why use it?
It reduces the effort of finding relevant internal information and showing where each conclusion came from.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it to search and read Notion sources, compare information, write summaries or reports, and publish the result back to Notion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cass-2003/local-workflow-skill/notion-research-documentation
Install

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.

Any agent
npx skills add cass-2003/local-workflow-skill --skill notion-research-documentation
Clone the repo
git clone --depth 1 https://github.com/cass-2003/local-workflow-skill

Made for: Codex.

Wrote 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.

agentmods badge for notion-research-documentation

README.md
[![agentmods](https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/notion-research-documentation/github.svg)](https://agentmods.dev/skills/cass-2003/local-workflow-skill/notion-research-documentation)
Your own site
<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/notion-research-documentation"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/notion-research-documentation/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.

agentmods 80×15 button for notion-research-documentation

Your own site · 80×15
<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/notion-research-documentation"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/notion-research-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 775 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.00775
Opus 5 $0.00019 $0.00387
Sonnet 5 $0.00008 $0.00155
Haiku 4.5 $0.00004 $0.00077

Measured 6d ago against content hash e88a46da978c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

notion-research-documentation 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 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.

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.

Origin

This is a copy

100% identical to notion-research-documentation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/content-authoring/codex/notion-research-documentation/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Research & Documentation

Pull relevant Notion pages, synthesize findings, and publish clear briefs or reports (with citations and links to sources).

Quick start

  1. Find sources with Notion:notion-search using targeted queries; confirm scope with the user.
  2. Fetch pages via Notion:notion-fetch; note key sections and capture citations (reference/citations.md).
  3. Choose output format (brief, summary, comparison, comprehensive report) using reference/format-selection-guide.md.
  4. Draft in Notion with Notion:notion-create-pages using the matching template (quick, summary, comparison, comprehensive).
  5. Link sources and add a references/citations section; update as new info arrives with Notion:notion-update-page.

Workflow

0) If any MCP call fails because Notion MCP is not connected, pause and set it up:

  1. Add the Notion MCP:
    • codex mcp add notion --url https://mcp.notion.com/mcp
  2. Enable remote MCP client:
    • Set [features].rmcp_client = true in config.toml or run codex --enable rmcp_client
  3. Log in with OAuth:
    • codex mcp login notion

After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.

1) Gather sources

  • Search first (Notion:notion-search); refine queries, and ask the user to confirm if multiple results appear.
  • Fetch relevant pages (Notion:notion-fetch), skim for facts, metrics, claims, constraints, and dates.
  • Track each source URL/ID for later citation; prefer direct quotes for critical facts.

2) Select the format

  • Quick readout → quick brief.
  • Single-topic dive → research summary.
  • Option tradeoffs → comparison.
  • Deep dive / exec-ready → comprehensive report.
  • See reference/format-selection-guide.md for when to pick each.

3) Synthesize

  • Outline before writing; group findings by themes/questions.
  • Note evidence with source IDs; flag gaps or contradictions.
  • Keep user goal in view (decision, summary, plan, recommendation).

Read the full file on GitHub · 60 lines

Changes

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.

  1. 6d ago First seen · 60 lines · 38 tokens per session scan A e88a46da978c

Subscribe to this mod's changes

notion-research-documentation is a skill published in the GitHub repository cass-2003/local-workflow-skill (12 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 775 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to notion-research-documentation, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens