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 makenotion/notion-cookbook --skill research-documentationgit clone --depth 1 https://github.com/makenotion/notion-cookbookWrote 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/makenotion/notion-cookbook/research-documentation)<a href="https://agentmods.dev/skills/makenotion/notion-cookbook/research-documentation"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/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/makenotion/notion-cookbook/research-documentation"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/research-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.00955 |
| Opus 5.5 | $0.00020 | $0.00382 |
| Sonnet 5.5 | $0.00010 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00096 |
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 21d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- notion-research-documentation — 100% identical, 140 lines differ
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research and documentation
Answer the user's question with supported findings, appropriate depth, and clear source attribution. Save or update a Notion document when requested.
Workflow
- Define the question and deliverable. Use the requested scope, audience, recency, and destination. A quick answer need not become a formal report. Resolve ambiguities that would change the research; proceed with stated, reasonable assumptions for minor details.
- Retrieve evidence selectively. Fetch supplied source URLs directly. Search only for missing evidence, starting with specific terms and known scope. Prioritize authoritative sources and fetch important matches before relying on them. Reuse sources already read; deduplicate results. Broaden or try synonyms when evidence is insufficient. For comprehensive requests, cover each requested dimension and relevant counterevidence rather than stopping at the first match.
- Reconcile and synthesize. Track which source supports each material finding. Distinguish adopted decisions from proposals and historical context. Check effective dates and explicit supersession; last-edited time alone does not make a claim current. Surface conflicts and missing evidence. Verify current external facts with available web tools when relevant; without them, disclose that limit.
- Write at the requested depth. Lead with the answer, explain the evidence, and separate findings from inference or recommendations. Cite material claims near the relevant text. Use Notion page mentions in Notion output and ordinary links for external sources or chat. Stop retrieval when the question is covered and material conflicts are resolved or explicitly reported; no minimum source count or word count is required.
- Deliver and verify. Return the answer in chat or write to the requested Notion destination. Fetch a target database's schema once, select the correct data source, and use actual property names and options. Update the specified report without replacing unrelated content. If placement is unspecified for a save request, use an established location or clarify material ambiguity. Check the write result and return the page link; read back unclear updates. Report incomplete research or writes rather than claiming success.
What ships with it
25 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.
- evaluations/basic-research.json 1.3 KB
- evaluations/discover-and-synthesize.json 3.3 KB
- evaluations/feedback-counts-and-segments.json 2.0 KB
- evaluations/feedback-unknown-identities.json 2.1 KB
- evaluations/quick-answer.json 723 B
- evaluations/README.md 2.7 KB
- evaluations/research-to-database.json 1.8 KB
- evaluations/restricted-search.json 1.3 KB
- evaluations/update-report.json 891 B
- examples/competitor-analysis.md 8.4 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 2.9 KB
- reference/citations.md 5.2 KB
- reference/comparison-format.md 896 B
- reference/comparison-template.md 1.1 KB
- reference/comprehensive-report-format.md 1.1 KB
- reference/comprehensive-report-template.md 1.4 KB
- reference/customer-feedback.md 2.3 KB
- reference/format-selection-guide.md 1.7 KB
- reference/quick-brief-format.md 804 B
- reference/quick-brief-template.md 614 B
- reference/research-summary-format.md 866 B
- reference/research-summary-template.md 1.3 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.
- 21d ago Changed · -19 lines · +2 tokens per session 94de2822bcb5
- 1mo ago First seen · 97 lines · 47 tokens per session scan A 05175c669c1f
notion-research-documentation is a skill published in the GitHub repository makenotion/notion-cookbook (220 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 955 once invoked, about $0.0002 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…