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 tommy-ca/notion-skills --skill research-documentationgit clone --depth 1 https://github.com/tommy-ca/notion-skillsWrote 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/tommy-ca/notion-skills/research-documentation)<a href="https://agentmods.dev/skills/tommy-ca/notion-skills/research-documentation"><img src="https://agentmods.dev/badge/skills/tommy-ca/notion-skills/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/tommy-ca/notion-skills/research-documentation"><img src="https://agentmods.dev/badge/skills/tommy-ca/notion-skills/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.00017 | $0.00715 |
| Opus 5 | $0.00009 | $0.00358 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
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 10d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
The Research Documentation skill automates the process of researching topics and capturing findings in a well-organized Notion database. It streamlines research by structuring information, tracking sources, and connecting related findings.
When to Use
Use this skill when you need to:
- Research complex topics and document findings
- Compile competitive analysis or market research
- Create literature reviews or research summaries
- Build knowledge bases around specific topics
- Track sources and citations
- Organize research across multiple domains
- Create research reports with sourced information
Features
- Structured Research Capture: Automatically organizes research findings with proper hierarchy
- Source Tracking: Maintains complete source attribution and citations
- Topic Organization: Categorizes findings by theme and relevance
- Cross-referencing: Connects related research across topics
- Evidence Collection: Captures quotes, data, and supporting evidence
- Research Timeline: Tracks how understanding evolved during research
Requirements
- Notion API Access: For creating and updating research documentation
- Research Database: Notion database structure for organizing findings
- Web Access: For gathering information from online sources
- Citation Format Preference: Configured citation style (APA, MLA, Chicago, etc.)
Implementation Details
This skill orchestrates research workflows by:
- Breaking down research topics into focused areas
- Gathering information from multiple sources
- Analyzing and synthesizing findings
- Organizing findings with proper attribution
- Creating relationships between related research
- Generating summary documents and reports
Research Documentation Workflow
Research Topic/Question
↓
Break into Research Areas
↓
Gather Information
↓
Analyze & Synthesize
↓
Extract Key Findings
↓
Organize with Sources
↓
Create Notion Documentation
↓
Output: Research Summary
What ships with it
2 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.
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.
- 10d ago First seen · 118 lines · 17 tokens per session scan A 52ef342bd49e
research-documentation is a skill published in the GitHub repository tommy-ca/notion-skills (62 stars, last pushed 10mo ago), licensed MIT. It adds 17 tokens to every session and 715 once invoked, about $0.0001 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
ara-research-manager
Records research provenance as a post-task epilogue, scanning conversation history at the end of a coding or research session to extract decisions, experiments, dead ends, claims, heuristics, and pivots, and writing them into the ara/ directory with user-vs-AI provenance tags. Use as a session epilogue — never during…
loop-engineering
Use when a repeatable task must become a bounded Trigger -> Execute -> Verify -> State loop, scheduled automation, goal agent, or metric-driven research cycle.
Wikimate Lint
A read-only checker for an organised notes vault, such as an Obsidian collection, and its Notion index. It looks for duplicates, broken links, isolated notes, and missing or invalid metadata.
agent-teams-command
Use when work has genuinely independent streams or distinct builder, evaluator, domain, and integration roles that require bounded multi-agent command scaled from 5 to 100+ agents.
agentic-engineering
Use when designing or refactoring a model-native engineering workflow with bounded autonomy, probes, custom evaluation, durable state, and verified write-back.
graph-engineering
Use when a workflow has explicit data dependencies, independently executable branches, typed joins, or node-local recovery needs that justify a bounded static dependency graph.