Borrowing it
Nothing to install: this file belongs to khanxxy/obsidian-second-brain. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/khanxxy/obsidian-second-brain/main/AGENTS.mdgit clone --depth 1 https://github.com/khanxxy/obsidian-second-brainWrote 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/khanxxy/obsidian-second-brain/agents-md)<a href="https://agentmods.dev/instructions/khanxxy/obsidian-second-brain/agents-md"><img src="https://agentmods.dev/badge/instructions/khanxxy/obsidian-second-brain/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.1 | $0.01829 | $0.01829 |
| Opus 5 | $0.00915 | $0.00915 |
| Sonnet 5 | $0.00366 | $0.00366 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
obsidian-second-brain 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 2d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Universal Agent Instructions
If you are an AI agent and this file was loaded automatically, follow it strictly.
Core idea: this vault is the source of truth. Do not let useful context stay only in chat.
New User Onboarding Protocol
If the user asks you to inspect, clone, set up, explain, or "check" this repo for the first time, do this before making edits:
- Read
README.md,START-HERE.md,VAULT.md, and thisAGENTS.md. - Tell the user, in plain language, what this repo is:
- an Obsidian Second Brain template
- built for humans and AI agents
- centered on
NOW.md, projectHANDOFF.md, and!1 Work Log/ - designed to prevent context loss between sessions
- Tell the user the first practical steps:
- open the folder as an Obsidian vault
- fill in
People/Me.md - create one project from
Projects/.template/ - add that project to
NOW.md - start future sessions from
NOW.md
- Ask for the user's first project name and one-sentence goal before creating or editing project files.
- After the user answers, help set up only that first project:
- copy
Projects/.template/toProjects/<Project Name>/ - fill
Context.mdfrom the user's answers - add the project to
NOW.md - add an initial
HANDOFF.mdentry - create or update today's
!1 Work Log/YYYY-MM-DD.md
- copy
- Offer skill installation only after the basic vault is understandable:
bash scripts/install-skill.sh
Do not silently fill the vault with fake content. Keep the first setup small and real.
Suggested first response:
This is an Obsidian Second Brain template for working with AI agents. The main workflow is: keep current state in NOW.md, keep project continuity in each project HANDOFF.md, and record sessions in !1 Work Log. I will first help you set up one real project. What should your first project be called, and what is its one-sentence goal?
Reading Order
At the start of a vault-related session, read in this order:
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.
- 2d ago Changed · +8 lines · +45 tokens per session f411fd4d42d1
- 6d ago First seen · 259 lines · 1,784 tokens per session scan A 201676804af9
obsidian-second-brain AGENTS.md is an instructions file published in the GitHub repository khanxxy/obsidian-second-brain (2 stars, last pushed 5d ago), licensed MIT. It adds 1,829 tokens to every session, about $0.0091 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.