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/msapps-mobile/claude-plugins/notion-knowledge-capturenpx skills add MSApps-Mobile/claude-plugins --skill notion-knowledge-capturegit 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-knowledge-capture)<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/notion-knowledge-capture"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/notion-knowledge-capture.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.00050 | $0.01570 |
| Opus 5 | $0.00025 | $0.00785 |
| Sonnet 5 | $0.00010 | $0.00314 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
notion-knowledge-capture 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.
This is a copy
100% identical to notion-knowledge-capture — 9 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Capture
Transforms conversations, discussions, and insights into structured documentation in your Notion workspace. Captures knowledge from chat context, formats it appropriately, and saves it to the right location with proper organization and linking.
Quick Start
When asked to save information to Notion:
- Extract content: Identify key information from conversation context
- Structure information: Organize into appropriate documentation format
- Determine location: Use
Notion:notion-searchto find appropriate wiki page/database - Create page: Use
Notion:notion-create-pagesto save content - Make discoverable: Link from relevant hub pages, add to databases, or update wiki navigation so others can find it
Knowledge Capture Workflow
Step 1: Identify content to capture
From conversation context, extract:
- Key concepts and definitions
- Decisions made and rationale
- How-to information and procedures
- Important insights or learnings
- Q&A pairs
- Examples and use cases
Step 2: Determine content type
Classify the knowledge:
- Concept/Definition
- How-to Guide
- Decision Record
- FAQ Entry
- Meeting Summary
- Learning/Post-mortem
- Reference Documentation
Step 3: Structure the content
Format appropriately based on content type:
- Use templates for consistency
- Add clear headings and sections
- Include examples where helpful
- Add relevant metadata
- Link to related pages
Step 4: Determine destination
Where to save:
- Wiki page (general knowledge base)
- Specific project page (project-specific knowledge)
- Documentation database (structured docs)
- FAQ database (questions and answers)
- Decision log (architecture/product decisions)
- Team wiki (team-specific knowledge)
Step 5: Create the page
Use Notion:notion-create-pages:
- Set appropriate title
- Use structured content from template
- Set properties if in database
- Add tags/categories
- Link to related pages
What ships with it
10 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/conversation-to-faq.md 16 KB
- examples/decision-capture.md 3.5 KB
- examples/how-to-guide.md 2.8 KB
- reference/database-best-practices.md 2.8 KB
- reference/decision-log-database.md 2.0 KB
- reference/documentation-database.md 2.7 KB
- reference/faq-database.md 2.0 KB
- reference/how-to-guide-database.md 1.2 KB
- reference/learning-database.md 1.3 KB
- reference/team-wiki-database.md 927 B
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 · 204 lines · 50 tokens per session scan A bb9b46103ccd
notion-knowledge-capture is a skill published in the GitHub repository MSApps-Mobile/claude-plugins (9 stars, last pushed 9d ago), licensed MIT. It adds 50 tokens to every session and 1,570 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to notion-knowledge-capture, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
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.
doc-html-slide
발표용 슬라이드 덱을 브라우저에서 바로 열리는 단일 파일·자체 완결형(self-contained) HTML로 만들어 드립니다. 인포그래픽(차트·다이어그램·KPI)은 한국어 숫자·라벨이 100% 정확한 인라인 SVG로 직접 렌더링하고, 실사 히어로·일러스트 이미지는 Higgsfield MCP 또는 codex(gpt-image-2)로 생성합니다. 필요 시 doc-pptx 체이닝으로 PowerPoint에서 편집 가능한 .pptx까지 병행 산출합니다. 다음과 같은 요청 시 사용하세요: "발표 슬라이드 HTML로 만들어줘" "키노트 덱 단일 HTML 파일로 렌더해줘"…
finance-investor-relations
투자 유치를 위한 IR 피치덱과 3개년 재무 모델(매출 예측·손익·현금흐름·밸류에이션)을 만들어 드립니다. 다음과 같은 요청 시 사용하세요: "IR 덱 만들어줘" "투자자 피치 자료 써줘" "재무 모델 만들어줘" "매출 예측 좀 해줘" "밸류에이션 계산해줘" "시리즈 A 투자 유치 자료 준비해줘" "투자자 보고서 정리해줘" 투자 단계(Pre-SeedSeries B)에 맞춘 12슬라이드 피치덱·재무 모델·예상 질문 Q&A를 만들고, PPT/엑셀 변환으로 이어집니다.
doc-html-report
마크다운 보고서를 그대로 브라우저에서 열리는 단일 파일 HTML로 바꿔 드립니다. 외부 라이브러리 없이 한 파일로 완결돼 이메일 첨부·인쇄·오프라인 열람이 됩니다. 다음과 같은 요청 시 사용하세요: "이 보고서 HTML 파일로 만들어줘" "주간 현황 보고서를 하나의 HTML로 렌더해줘" "재무제표를 HTML 보고서로 변환해줘" "인시던트 리포트를 HTML로 정리해줘" "프린트 가능한 사업계획서 HTML로 만들어줘" "이메일에 붙일 수 있는 HTML 리포트 만들어줘" 현황·인시던트·사업계획·설명서·재무·PR 6종 서식을 갖췄고, 보고서 종류에 맞춰 자동으로 골라…
doc-pptx
발표용 파워포인트(.pptx) 슬라이드를 디자인해 바로 열리는 파일로 만들어 드립니다 — 사내 보고, 투자 피칭, 교육자료, 컨퍼런스 키노트까지. 다음과 같은 요청 시 사용하세요: "발표자료 PPT로 만들어줘" "파워포인트 슬라이드 디자인해줘" "보고서를 발표용 PPT로 만들어줘" "투자 피칭 덱 15장 만들어줘" "임원 보고용 슬라이드 격식 있게" "신입사원 교육자료 PPT" "제품 데모 슬라이드 깔끔하게 디자인해줘" 한국형 폰트·색 팔레트 디자인 시스템과 비즈니스 슬라이드 구성안을 적용해 슬라이드를 만들고, 카피는 AI 슬롭 검수로 다듬을 수 있습니다.…
consult-gov-grant
나에게 맞는 정부·공공기관 지원사업을 찾아주고, 심사 기준에 맞춘 사업계획서·신청서 초안을 만들어 드립니다(Word·한글·Excel 파일까지). 창업자·소상공인·중소기업·연구자·비영리단체·개인 누구나 쓸 수 있습니다. 다음과 같은 요청 시 사용하세요: "정부 지원사업 찾아줘" "우리 상황에 맞는 지원금 있어?" "사업계획서 초안 써줘" "지원서 작성 도와줘" "이 신청서 심사 기준으로 검토해줘" "마감 전에 뭐 준비해야 해?" "예비창업패키지 신청서 만들어줘" "지원금 어떻게 쓰는지 모르겠어" 지원사업 탐색·신청서 작성·서류 검토·일정 관리까지 도와주며, 마지막에…