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 skills add MSApps-Mobile/claude-plugins --skill notion-research-documentationgit clone --depth 1 https://github.com/MSApps-Mobile/claude-pluginsWrote 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/msapps-mobile/claude-plugins/notion-research-documentation)<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/notion-research-documentation"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/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.
<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/notion-research-documentation"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/notion-research-documentation.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00047 | $0.00778 |
| Opus 5.5 | $0.00019 | $0.00311 |
| Sonnet 5.5 | $0.00009 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
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 1mo 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.
This is a copy
100% identical to notion-research-documentation — 140 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research & Documentation
Enables comprehensive research workflows: search for information across your Notion workspace, fetch and analyze relevant pages, synthesize findings, and create well-structured documentation.
Quick Start
When asked to research and document a topic:
- Search for relevant content: Use
Notion:notion-searchto find pages - Fetch detailed information: Use
Notion:notion-fetchto read full page content - Synthesize findings: Analyze and combine information from multiple sources
- Create structured output: Use
Notion:notion-create-pagesto write documentation
Research Workflow
Step 1: Search for relevant information
Use Notion:notion-search with the research topic
Filter by teamspace if scope is known
Review search results to identify most relevant pages
Step 2: Fetch page content
Use Notion:notion-fetch for each relevant page URL
Collect content from all relevant sources
Note key findings, quotes, and data points
Step 3: Synthesize findings
Analyze the collected information:
- Identify key themes and patterns
- Connect related concepts across sources
- Note gaps or conflicting information
- Organize findings logically
Step 4: Create structured documentation
Use the appropriate documentation template (see reference/format-selection-guide.md) to structure output:
- Clear title and executive summary
- Well-organized sections with headings
- Citations linking back to source pages
- Actionable conclusions or next steps
Output Formats
Choose the appropriate format based on request:
Research Summary: See reference/research-summary-format.md Comprehensive Report: See reference/comprehensive-report-format.md Quick Brief: See reference/quick-brief-format.md
Best Practices
- Cast a wide net first: Start with broad searches, then narrow down
- Cite sources: Always link back to source pages using mentions
- Verify recency: Check page last-edited dates for current information
- Cross-reference: Validate findings across multiple sources
- Structure clearly: Use headings, bullets, and formatting for readability
What ships with it
15 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.
- examples/competitor-analysis.md 8.0 KB
- examples/market-research.md 1.9 KB
- examples/technical-investigation.md 6.4 KB
- examples/trip-planning.md 3.7 KB
- reference/advanced-search.md 4.5 KB
- reference/citations.md 5.0 KB
- reference/comparison-format.md 870 B
- reference/comparison-template.md 911 B
- reference/comprehensive-report-format.md 1.1 KB
- reference/comprehensive-report-template.md 1.2 KB
- reference/format-selection-guide.md 2.7 KB
- reference/quick-brief-format.md 767 B
- reference/quick-brief-template.md 473 B
- reference/research-summary-format.md 841 B
- reference/research-summary-template.md 1.1 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.
- 1mo ago First seen · 94 lines · 47 tokens per session scan A a7a9e267998c
notion-research-documentation is a skill published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 778 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to notion-research-documentation, differing in 140 lines, and is treated as a copy.
Other skills, from other repositories
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.
media-gemini-3-image-prompt
A prompt builder for Gemini 3 Pro Image, also known as Nano Banana Pro, Google's image-generation model. It expands a short request into five parts covering the subject, action, setting, composition, lighting, style, and text constraints.
data-realestate
A lookup tool for reported South Korean property transactions using Ministry of Land data. It covers sales and rental deals for apartments, officetels, multi-family homes, houses, and commercial or office properties.
design-sync-upload
An uploader for design-system files such as DESIGN.md, tokens, logos, fonts, and images into Claude Design. It can either use an authenticated connection or prepare a folder and guide for manual upload.
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.