Borrowing it
Nothing to install: this file belongs to aliasunder/vault-cortex. 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/aliasunder/vault-cortex/main/AGENTS.mdgit clone --depth 1 https://github.com/aliasunder/vault-cortexWrote 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/aliasunder/vault-cortex/agents-md)<a href="https://agentmods.dev/instructions/aliasunder/vault-cortex/agents-md"><img src="https://agentmods.dev/badge/instructions/aliasunder/vault-cortex/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/aliasunder/vault-cortex/agents-md"><img src="https://agentmods.dev/badge/instructions/aliasunder/vault-cortex/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.21334 | $0.21334 |
| Opus 5.5 | $0.08534 | $0.08534 |
| Sonnet 5.5 | $0.04267 | $0.04267 |
| Haiku 4.5 | $0.02133 | $0.02133 |
Grade A, and why
vault-cortex 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 — 1,459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project conventions for AI-assisted development on vault-cortex — for Claude Code and other AI agents.
What this project is
Remote MCP server exposing an Obsidian vault over HTTPS. One two-target
Dockerfile builds the ghcr.io/aliasunder/vault-cortex image: the local
target (:latest, the default stage) is tini + the MCP server alone; the
remote target (:remote) adds s6-overlay supervising both obsidian-sync
(bidirectional Obsidian Sync via the obsidian-headless npm CLI) and the MCP
server in a single container — s6 service definitions live in rootfs/, and
the init chain registers the initial Sync device under the DEVICE_NAME env
var, or the container hostname when unset. Both
processes run as UID 1000 (PUID/PGID-adjustable). Production runs the
:remote image on Lightsail as a single Compose service, fronted by API
Gateway: OAuth endpoints and /healthz pass straight through, and every
other route goes through a Lambda authorizer that validates the static
token or JWT.
IaC via SST v4.
The server provides vault CRUD, hybrid search (FTS5 keyword and sqlite-vec
vector results fused by Reciprocal Rank Fusion, then reranked by a
cross-encoder; the vector and rerank stages are optional via
EMBEDDING_ENABLED and RERANK_MODE; see ARCHITECTURE.md → Hybrid Search),
and an optional memory layer (dated-entry notes in the vault's About Me/
folder by default, set by MEMORY_DIR). The Docker image uses Debian
slim (node:24-trixie-slim) because onnxruntime-node requires glibc,
and specifically trixie because better-sqlite3 v13's bundled linux-arm64
prebuild needs glibc >= 2.38 (bookworm's 2.36 crash-loops arm64 images).
All solutions must be portable — they can't rely on one-off manual fixes, hardcoded paths, or user-specific configuration. If it works only on the author's machine, it's not done.
Design for the Obsidian user. The end user is always an Obsidian user, so
anything that mirrors an Obsidian concept — backlinks, outgoing links, orphans,
the graph, tags, properties, daily notes — must match what Obsidian itself does.
At minimum, recognize every form Obsidian recognizes; behavior that is a strict
subset of Obsidian's is a bug, not a limitation. For link resolution
specifically, that means all of Obsidian's link styles ([[wikilink]],
[[wikilink|alias]], [[wikilink#heading]], ![[embed]], [md](path.md),
),
links in frontmatter properties (e.g. related:), and all three "New link
format" modes — shortest path, path from vault folder, and path from current
file (including relative ../ paths).
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 Changed · +5 lines · +3 tokens per session 9c503dbad48b
- 6d ago Changed · +2 lines · +13 tokens per session 0f81326d7c01
- 7d ago Changed · +10 lines · +149 tokens per session f1c4f8f39680
- 8d ago Changed · +21 lines · +297 tokens per session d27d4ea58d5d
- 10d ago Changed · +2 lines · +38 tokens per session 7abd3dae0e92
- 17d ago Changed · +12 lines · +158 tokens per session fd74f5d32806
- 18d ago Changed · +5 lines · +90 tokens per session e493f8d3a5ae
- 20d ago Changed · +8 lines · +139 tokens per session 7f58f64442e8
- 22d ago Changed · +5 lines · +165 tokens per session d706926ccbee
- 23d ago First seen · 1,389 lines · 20,282 tokens per session scan A 9a60e459485e
vault-cortex AGENTS.md is an instructions file published in the GitHub repository aliasunder/vault-cortex (32 stars, last pushed today), licensed MIT. It adds 21,334 tokens to every session, about $0.0853 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.