What is obsidian_vault_pipeline AGENTS.md?

Repository instructions for a Rust version of the Obsidian Vault Pipeline, including its source of truth, folder layout, architecture boundaries, and development commands. They explain that the current implementation is Rust-based and that the older Python implementation is no longer part of the tracked project.

Use them when changing the pipeline, checking the expected repository structure, or running Rust metadata, tests, and code-quality checks.

They prevent developers from relying on outdated Python files or legacy documentation. They also provide a consistent reference for where code belongs and how to build and test it.

How fakechris/obsidian_vault_pipeline configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to fakechris/obsidian_vault_pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/fakechris/obsidian_vault_pipeline/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/fakechris/obsidian_vault_pipeline

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/fakechris/obsidian_vault_pipeline/agents-md/github.svg)](https://agentmods.dev/instructions/fakechris/obsidian_vault_pipeline/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/fakechris/obsidian_vault_pipeline/agents-md"><img src="https://agentmods.dev/badge/instructions/fakechris/obsidian_vault_pipeline/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/fakechris/obsidian_vault_pipeline/agents-md"><img src="https://agentmods.dev/badge/instructions/fakechris/obsidian_vault_pipeline/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 923 This file is loaded in full into every session.

When invoked 923 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00923	$0.00923
Opus 5	$0.00462	$0.00462
Sonnet 5	$0.00185	$0.00185
Haiku 4.5	$0.00092	$0.00092

Measured 9d ago against content hash 4f46e8c7a371, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

obsidian_vault_pipeline 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 9d 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.

AGENTS.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md - OVP Next Rust Trunk

This branch is the Rust OVP Next trunk. The repository root is the Rust workspace root.

Source Of Truth

Build and architecture decisions must start from the Rust crates under crates/.
Cargo.toml, Cargo.lock, crates/, fixtures/, manifests/, scripts/, and Rust-focused docs/ are the current implementation surface.
The legacy Python implementation has been removed from this branch's tracked working tree.
Do not infer current architecture from Python-era files, old vault templates, or legacy product docs.
Do not reintroduce a Python pipeline, Python package metadata, or Python CLI wrappers unless the user explicitly requests a migration helper script.

Repository Shape

Expected root layout:

Cargo.toml
Cargo.lock
crates/
docs/
fixtures/
manifests/
scripts/
README.md
.gitignore
AGENTS.md

There should be no nested rust/ovp2/ project and no root src/ovp_pipeline/, pyproject.toml, requirements.txt, or MANIFEST.in.

Development Commands

Run from the repository root:

cargo metadata --no-deps --format-version 1
cargo test --workspace
cargo clippy --workspace --all-targets -- -D warnings
bash scripts/check_architecture.sh

Use rg for searches. Prefer git mv and git rm for structural edits so migrations remain auditable.

Architecture Boundaries

ovp-core owns the sync kernel primitives.
ovp-domain owns domain types, transforms, prompts, fixtures, and contract parsing.
ovp-app owns manifest-based graph assembly.
ovp-run owns the operational run cycle.
ovp-query, ovp-lint, ovp-rag, ovp-auto, ovp-eval, and ovp-review are read, health, automation, comparison, and review layers around the run cycle.
ovp-cli is a thin argument-parsing layer that delegates into the crates above.

Derived state must stay rebuildable from Rust code and committed fixtures/contracts. Historical legacy alignment docs can be used as behavioral context, not as runtime authority.

Read the full file on GitHub · 91 lines

Changes

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.

9d ago First seen · 91 lines · 923 tokens per session scan A 4f46e8c7a371

Subscribe to this mod's changes

obsidian_vault_pipeline AGENTS.md is an instructions file published in the GitHub repository fakechris/obsidian_vault_pipeline (163 stars, last pushed yesterday), licensed Apache-2.0. It adds 923 tokens to every session, about $0.0046 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.

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

obsidian_vault_pipeline: Instructions file for Codex