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 instructions/nyosegawa/notion-cli/agents-mdgit clone --depth 1 https://github.com/nyosegawa/notion-cliWrote 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/instructions/nyosegawa/notion-cli/agents-md)<a href="https://agentmods.dev/instructions/nyosegawa/notion-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/nyosegawa/notion-cli/agents-md.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.00895 | $0.00895 |
| Opus 5 | $0.00447 | $0.00447 |
| Sonnet 5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
notion-cli AGENTS.md 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ncli
Notion MCP + REST API 対応の CLI。MCP は OAuth、REST API は Integration Token で認証。
Commands
npm run build && npm run typecheck && npm run lint && npm test
Structure
docs/— 設計 (architecture, commands, auth, design-decisions, agent-first-design)docs/agent-first-design.md— Agent-first CLI 設計思想 (出力・ディスカバリ・エラーの設計原則)research/— 調査結果 (事実のみ)skills/— Agent Skills (skills/notion/— ncli 活用スキル)src/rest/— REST API クライアント (client, with-rest-client)PHASE.md— フェーズ計画 (チェックボックスで進捗追跡)
Phase Workflow
PHASE-N 指定時:
PHASE.md読み → 未完了項目確認 (前フェーズの備考も必読)docs/commands.mdで CLI 仕様確認research/01-notion-remote-mcp-tools.mdで MCP ツールの実際の inputSchema を確認 (引数名はここが正)- 既存コマンド (
src/commands/search.ts等) のパターンを踏襲:buildXxxCall()純粋関数で CLI→MCP 引数マッピングwithConnection()ヘルパーで接続ボイラープレートprintOutput()+cmd.optsWithGlobals()で--json/--raw対応--dataフラグで JSON 直接指定 (他フラグを上書き)
- テスト先行 → 実装 →
npm run build && npm run typecheck && npm run lint && npm test通過 - 完了項目を
[x]に更新、全完了でフェーズ見出しに ✅ - 変更を commit & push (コミットメッセージは変更内容を要約)
Rules
biome.jsonを編集しない--no-verifyを使わない- テストを書いてから実装 (テストが仕様)
ncli apiescape hatch を常に維持- エラーは
CliError(What + Why + Hint パターン)。プロダクションコードでnew Error()は使わない - 出力は
--json/--raw対応必須。デフォルトは JSON テキストを pretty-print - MCP の
isErrorレスポンスはCliErrorに変換 (agent-recoverable なヒント付き) --dataの JSON パースエラーはparseJsonData()ヘルパー経由で CliError に統一- MCP ツール引数名は公式ドキュメントではなく
research/01-notion-remote-mcp-tools.mdの inputSchema が正 - MCP ツール名を CLI のインターフェースとして露出しない(
ncli apiの escape hatch のみ) - REST API エラーも
CliErrorに変換 (restErrorToCliError())。REST コマンドの出力はprintRestOutput()を使用 - 設計原則の詳細は
docs/agent-first-design.mdを参照
Testing
vitest(src/**/*.test.ts)、引数パース・マッピング優先- MCP 接続はモック (E2E は PHASE-5)
Harness
- PostToolUse:
biome check --fix自動実行 - PreToolUse:
biome.json/.claude/settings.json編集ブロック - Lefthook: pre-commit で lint + test
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 · 60 lines · 895 tokens per session scan A deb1138da8a3
notion-cli AGENTS.md is an instructions file published in the GitHub repository nyosegawa/notion-cli (55 stars, last pushed 5mo ago), licensed MIT. It adds 895 tokens to every session, about $0.0045 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.