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.
git clone --depth 1 https://github.com/luanpdd/kit-mcpWrote 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/commands/luanpdd/kit-mcp/setup-notion)<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/setup-notion"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/setup-notion.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.1 | $0.00000 | $0.00737 |
| Opus 5 | $0.00000 | $0.00368 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
setup-notion 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.
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.
/setup-notion — Inicializar Documentação Notion para um Projeto
Cria a estrutura de páginas Notion para um novo projeto sob a página raiz do seu workspace e gera o .claude/notion-config.json local.
Quando usar
Ao iniciar um novo projeto framework que ainda não tem página no Notion.
Execute uma vez por projeto — depois use /publicar normalmente.
Processo
Passo 1 — Ler contexto do projeto
Leia .planning/PROJECT.md para obter:
- Nome do projeto
- Stack
- Descrição em 1 frase
Passo 2 — Criar páginas no Notion
Use o Notion MCP (notion-create-pages) com parent.page_id = "{NOTION_PARENT_PAGE_ID}", onde NOTION_PARENT_PAGE_ID é o ID da página raiz do seu workspace de documentação (configure via env var KIT_NOTION_PARENT_PAGE_ID ou substitua diretamente).
Crie a página raiz do projeto com ícone 📋 e este conteúdo:
[Callout azul] {NOME_PROJETO} — {DESCRICAO_1_FRASE}
---
## Stack
[Tabela com camadas e tecnologias do PROJECT.md]
---
## Estrutura da Documentação
- changelog/ — Uma entrada por milestone
- features/ — O que cada feature faz
- adr/ — Decisões arquiteturais
- runbooks/ — Procedimentos operacionais
---
## Versões Lançadas
[Tabela vazia: Versão | Nome | Data | Status]
Depois crie as 4 subpáginas sob a página raiz criada:
- 📅
changelog/— com tabela de índice vazia - 📄
features/— com tabela de índice vazia - 🏛️
adr/— com tabela de índice vazia - 📖
runbooks/— com tabela de índice vazia
Passo 3 — Gerar notion-config.json
Com os IDs retornados pelo Notion MCP, crie .claude/notion-config.json:
{
"project": "{NOME_PROJETO}",
"notion": {
"root": "{ID_ROOT}",
"root_url": "{URL_ROOT}",
"changelog": "{ID_CHANGELOG}",
"features": "{ID_FEATURES}",
"adr": "{ID_ADR}",
"runbooks": "{ID_RUNBOOKS}"
}
}
Passo 4 — Reportar resultado
✅ Notion configurado para {NOME_PROJETO}
📋 Página principal: {URL_ROOT}
📅 changelog/: {URL_CHANGELOG}
📄 features/: {URL_FEATURES}
🏛️ adr/: {URL_ADR}
📖 runbooks/: {URL_RUNBOOKS}
Arquivo criado: .claude/notion-config.json
Próximo passo: use /publicar ao concluir o próximo milestone.
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 · 94 lines · 0 tokens per session scan A d1cd970ddecc
setup-notion is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 737 tokens. 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.