ObsidianDataWeave: Instructions file for Codex

AGENTS.md

ObsidianDataWeave AGENTS.md is an instructions file for Codex, OpenCode from howdeploy/ObsidianDataWeave. It costs 5,714 tokens per session, scanned A, original, MIT.

A project guide for turning Word documents, NotebookLM notebooks, Obsidian notes, and contact notes into Zettelkasten notes. Zettelkasten is a method of keeping small, linked notes, while an MOC is a map that organizes related notes.

In plain words
What is it for?
Processing DOCX files, curated NotebookLM notebooks, existing vault notes, and networking notes into atomic notes, maps of content, and individual contact cards.
Why use it?
It tells agents which scripts and safe options to use when converting different kinds of source material into organized notes, including how to handle conflicts.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; mentions Codex.

This is howdeploy/ObsidianDataWeave's own configuration. It tells Codex and OpenCode how to work on ObsidianDataWeave itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ObsidianDataWeave configures →

Reuse

Borrowing it

Nothing to install: this file belongs to howdeploy/ObsidianDataWeave. 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/howdeploy/ObsidianDataWeave/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/howdeploy/ObsidianDataWeave

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.

agentmods badge for ObsidianDataWeave AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/howdeploy/obsidiandataweave/agents-md/github.svg)](https://agentmods.dev/instructions/howdeploy/obsidiandataweave/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/howdeploy/obsidiandataweave/agents-md"><img src="https://agentmods.dev/badge/instructions/howdeploy/obsidiandataweave/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.

agentmods 80×15 button for ObsidianDataWeave AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/howdeploy/obsidiandataweave/agents-md"><img src="https://agentmods.dev/badge/instructions/howdeploy/obsidiandataweave/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5,714 This file is loaded in full into every session.
When invoked 5,714 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.05714 $0.05714
Opus 5.5 $0.02286 $0.02286
Sonnet 5.5 $0.01143 $0.01143
Haiku 4.5 $0.00571 $0.00571

Measured 1mo ago against content hash 46fd752ef67e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ObsidianDataWeave 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 1mo 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 · 315 lines

How it starts

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

ObsidianDataWeave Agent Contract

Purpose

This repository converts source .docx documents and existing Obsidian notes into Zettelkasten-style notes with MOC structure.

Agents should treat this file as the canonical integration contract for both Claude Code and Codex.

Supported Workflows

  1. Process a source document into atomic notes and MOC: python3 scripts/process.py "Document.docx" Safe automation form: python3 scripts/process.py "Document.docx" --non-interactive --on-conflict skip
  2. Process a curated NotebookLM notebook into atomic notes and MOC: python3 scripts/process_notebook.py "<notebook_id>" Safe automation form: python3 scripts/process_notebook.py "<notebook_id>" --non-interactive --on-conflict skip Optional inputs: --include-sources, --include-mindmap, --profile <name>.
  3. Process an existing personal note in the vault: python3 scripts/process_note.py "Note Title" Safe automation form: python3 scripts/process_note.py "Note Title" --mode atomize --non-interactive --on-conflict skip
  4. Process a contacts/networking note into individual contact cards: python3 scripts/process_contacts.py "Contacts Note" Safe automation form: python3 scripts/process_contacts.py "Contacts Note" --non-interactive --on-conflict skip
  5. Generate markdown files from an existing atom plan JSON: python3 scripts/generate_notes.py /path/to/atom-plan.json
  6. Copy staged markdown files into the vault: python3 scripts/vault_writer.py --staging /path/to/staging --atom-plan /path/to/atom-plan.json
  7. Find duplicate note candidates or run semantic dedup: python3 scripts/dedup_vault.py --dry-run
  8. Run environment checks before operating on the vault: python3 scripts/doctor.py
  9. Run deep research directly into a NotebookLM notebook (bypasses the upstream CLI retry duplication bug, see "Why research_notebook.py exists" below): python3 scripts/research_notebook.py run "<notebook_id>" "<query>" Safe automation form: python3 scripts/research_notebook.py run "<notebook_id>" "<query>" --non-interactive Dry-run preview of what would be imported: python3 scripts/research_notebook.py run "<notebook_id>" "<query>" --dry-run
  10. Clean up duplicate/error sources in an existing NotebookLM notebook: python3 scripts/research_notebook.py dedupe "<notebook_id>" --dry-run Safe automation form: python3 scripts/research_notebook.py dedupe "<notebook_id>" --include-error --non-interactive
  11. Initialize a new LLM Wiki space: python3 scripts/wiki_init.py <slug> --mode project --title "Project" Modes: project (fixed core pages) or corpus (entities-only). Add --lang ru (or --lang en) to pick template language; defaults to [wiki].default_lang in config.toml (en if unset).
  12. Ingest raw inputs into a wiki-space: python3 scripts/wiki_ingest.py <slug> <file-or-dir> --kind {articles|docs|transcripts|assets}
  13. Compile a wiki-space (LLM merges raw into pages): python3 scripts/wiki_compile.py <slug> --since-last-compile Safe automation form: python3 scripts/wiki_compile.py <slug> --since-last-compile --on-conflict overwrite
  14. Update one page from a single new raw input (incremental merge): python3 scripts/wiki_update.py <slug> raw/docs/<file>.md
  15. Lint wiki-space integrity: python3 scripts/wiki_lint.py [<slug>] [--strict]
  16. Search the FTS5 vault memory (lexical full-text over every note): python3 scripts/memory_index.py search "<query>" --json Useful flags: --limit N, --prefix (last term as prefix), --folder X, --tag Y, --raw (raw FTS5 syntax). The index updates automatically after each vault_writer write ([memory].auto_update).
  17. Build or refresh the memory index / run the upgrade migration: python3 scripts/memory_index.py build | update | status python3 scripts/migrate.py (idempotent: adds [memory] config, builds index)

Read the full file on GitHub · 315 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.

  1. 1mo ago First seen · 315 lines · 5,714 tokens per session scan A 46fd752ef67e

Subscribe to this mod's changes

ObsidianDataWeave AGENTS.md is an instructions file published in the GitHub repository howdeploy/ObsidianDataWeave (57 stars, last pushed 1mo ago), licensed MIT. It adds 5,714 tokens to every session, about $0.0229 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.

Related

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

microsoft/vscode · 9,715 tokens

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,581 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens