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/howdeploy/obsidiandataweave/agents-mdgit clone --depth 1 https://github.com/howdeploy/ObsidianDataWeaveWrote 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/howdeploy/obsidiandataweave/agents-md)<a href="https://agentmods.dev/instructions/howdeploy/obsidiandataweave/agents-md"><img src="https://agentmods.dev/badge/instructions/howdeploy/obsidiandataweave/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 | $0.05714 | $0.05714 |
| Opus 5 | $0.02857 | $0.02857 |
| Sonnet 5 | $0.01143 | $0.01143 |
| Haiku 4.5 | $0.00571 | $0.00571 |
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 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 — 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
- 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 - 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 skipOptional inputs:--include-sources,--include-mindmap,--profile <name>. - 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 - 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 - Generate markdown files from an existing atom plan JSON:
python3 scripts/generate_notes.py /path/to/atom-plan.json - Copy staged markdown files into the vault:
python3 scripts/vault_writer.py --staging /path/to/staging --atom-plan /path/to/atom-plan.json - Find duplicate note candidates or run semantic dedup:
python3 scripts/dedup_vault.py --dry-run - Run environment checks before operating on the vault:
python3 scripts/doctor.py - 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-interactiveDry-run preview of what would be imported:python3 scripts/research_notebook.py run "<notebook_id>" "<query>" --dry-run - Clean up duplicate/error sources in an existing NotebookLM notebook:
python3 scripts/research_notebook.py dedupe "<notebook_id>" --dry-runSafe automation form:python3 scripts/research_notebook.py dedupe "<notebook_id>" --include-error --non-interactive - Initialize a new LLM Wiki space:
python3 scripts/wiki_init.py <slug> --mode project --title "Project"Modes:project(fixed core pages) orcorpus(entities-only). Add--lang ru(or--lang en) to pick template language; defaults to[wiki].default_langinconfig.toml(enif unset). - Ingest raw inputs into a wiki-space:
python3 scripts/wiki_ingest.py <slug> <file-or-dir> --kind {articles|docs|transcripts|assets} - Compile a wiki-space (LLM merges raw into pages):
python3 scripts/wiki_compile.py <slug> --since-last-compileSafe automation form:python3 scripts/wiki_compile.py <slug> --since-last-compile --on-conflict overwrite - Update one page from a single new raw input (incremental merge):
python3 scripts/wiki_update.py <slug> raw/docs/<file>.md - Lint wiki-space integrity:
python3 scripts/wiki_lint.py [<slug>] [--strict] - Search the FTS5 vault memory (lexical full-text over every note):
python3 scripts/memory_index.py search "<query>" --jsonUseful 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). - Build or refresh the memory index / run the upgrade migration:
python3 scripts/memory_index.py build|update|statuspython3 scripts/migrate.py(idempotent: adds [memory] config, builds index)
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 · 315 lines · 5,714 tokens per session scan A 46fd752ef67e
ObsidianDataWeave AGENTS.md is an instructions file published in the GitHub repository howdeploy/ObsidianDataWeave (49 stars, last pushed 2mo ago), licensed MIT. It adds 5,714 tokens to every session, about $0.0286 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
mcp-pandoc AGENTS.md
Instructions for vivekVells/mcp-pandoc, covering agents.md, what this is, where things are, deeper context and commands.
agentic-resume-builder CLAUDE.md
Claude Code instructions for WtotdeD/agentic-resume-builder, covering agentic-resume-builder development guidelines, what this repo is, active technologies, package manager and validation.
fcp-sheets CLAUDE.md
Instructions for os-tack/fcp-sheets, covering fcp-sheets, project overview, architecture, key patterns and commands.
rodya-caijing-studio AGENTS.md
AGENTS.md instructions for nekopunch11/rodya-caijing-studio, covering rodya-caijing-studio · 给 ai agent 的使用说明, 入口与路由, 不可破的硬约束(合规灵魂,破了整套工具就失效), docx 渲染路由(财经内容台例外) and 在 codex 中安装.
paperless-ngx-mcp-server CLAUDE.md
Claude Code instructions for cbsmiley/paperless-ngx-mcp-server, covering claude.md, project overview, common commands, architecture and entry points.
hermes-procurement-pricing-mcp AGENTS.md
AGENTS.md instructions for felix-windsor/hermes-procurement-pricing-mcp, a project described as: Secure procurement quotation comparison MCP service with document parsing, mock market pricing, anomaly detection, and Telegram/Hermes integration.