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/makenotion/lore/agents-mdgit clone --depth 1 https://github.com/makenotion/loreWhat 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.03013 | $0.03013 |
| Opus 5 | $0.01507 | $0.01507 |
| Sonnet 5 | $0.00603 | $0.00603 |
| Haiku 4.5 | $0.00301 | $0.00301 |
Grade A, and why
lore 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 3d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Reference
Read this file first, then read the guide for the area you are working in. When a subsystem guide conflicts with this file, the subsystem guide wins for that subsystem.
Subsystem Guides
| Area | Guide | Scope |
|---|---|---|
| MCP server | src/mcp/AGENTS.md |
Tool registration, error handling, server startup |
| Domain services | src/core/AGENTS.md |
Service pattern, context resolution, fact invalidation |
| Notion SDK layer | src/notion/AGENTS.md |
Client, schema, extractors, vault setup, Notion doc routing |
| CLI | src/cli/AGENTS.md |
CLI routing, command inventory, detailed guide pointers |
| Hook runner | src/hooks/AGENTS.md |
Hook routing, handler registration, doc precedence |
| Auth layer | src/auth/AGENTS.md |
ntn / PAT auth, auth.json contract, vault preflight, token classification |
Detailed Guides
| Guide | Use it for |
|---|---|
docs/development.md |
Architecture, commands, conventions, stability rules, troubleshooting |
docs/authentication.md |
Auth priority chain, ntn behavior, auth.json contract, rate limits, troubleshooting |
docs/profiles.md |
Default profile selector, profile-owned taxonomy/schema/prompts, no-singleton threading |
docs/memory-workflows.md |
Lore memory/fact/decision/task workflow, topic keys, digest |
docs/conflict-detection.md |
lore conflicts scan workflow and compare-verdict contract |
docs/memory-debt.md |
lore debt scan / create-tasks audit categories, scoring, recommended maintenance cadence, idempotency contract |
docs/topology.md |
lore status topology section, health states, recovery workflow |
docs/topology-inheritance.md |
Read-upstream wake-up rendering, trust containment, design rules, opt-out behavior, promotion-target read-upstream carve-out |
docs/topology-promotion.md |
Promotion workflow, audit block, guards, dry run, source validation, idempotency, promoter identity, implementation pointers |
docs/notion-sdk-v5.md, docs/notion-rate-limit.md |
Notion SDK v5 shape differences, rate-limit gates, endpoint overrides, call-site checklist |
docs/hooks.md, docs/hooks-autosave.md, docs/hooks-wakeup.md, docs/hooks-background.md |
Installed hook behavior, shared-vault hook setup, and runtime-flow contracts |
docs/team-rollout.md |
Operator-facing ntn-first rollout runbook |
docs/ci.md |
Per-step CI contract: token/network/fixture needs and fork-safety rules |
docs/cli.md, docs/cli-authoring.md, docs/cli-command-contracts.md, docs/mcp-tools.md |
CLI and MCP user-facing reference, CLI authoring rules, command contracts |
docs/mcp-tool-authoring.md, docs/archive/mcp-tool-history.md |
MCP tool-authoring patterns and historical MCP release evidence |
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.
- 3d ago First seen · 211 lines · 3,013 tokens per session scan A 584447a6a403
lore AGENTS.md is an instructions file published in the GitHub repository makenotion/lore (87 stars, last pushed 29d ago), licensed MIT. It adds 3,013 tokens to every session, about $0.0151 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.