Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/howdeploy/deploychan_mcpnpx agentmods add skills/howdeploy/deploychan_mcp/obsidian-dataweaveWrote 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/skills/howdeploy/deploychan_mcp/obsidian-dataweave)<a href="https://agentmods.dev/skills/howdeploy/deploychan_mcp/obsidian-dataweave"><img src="https://agentmods.dev/badge/skills/howdeploy/deploychan_mcp/obsidian-dataweave/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/skills/howdeploy/deploychan_mcp/obsidian-dataweave"><img src="https://agentmods.dev/badge/skills/howdeploy/deploychan_mcp/obsidian-dataweave.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 104 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00072 | $0.01849 |
| Opus 5.5 | $0.00029 | $0.00740 |
| Sonnet 5.5 | $0.00014 | $0.00370 |
| Haiku 4.5 | $0.00007 | $0.00185 |
Grade A, and why
ObsidianDataWeave: NotebookLM, Atomization, and LLM Wiki 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ObsidianDataWeave
Turns Claude Code and Codex into a full control panel for NotebookLM and your Obsidian
vault. You run deep research, manage sources, and pull notes out of notebooks — all with a
single natural-language command. In parallel, it imports .docx from Google Drive and
atomizes them into Zettelkasten notes with a MOC, tags, and wikilinks. On top — an isolated
LLM Wiki layer (a compiled base in the Karpathy style), and FTS5 memory — a full-text
index of the entire vault without a single external dependency. Public: howdeploy/ObsidianDataWeave, MIT.
Both clients are supported natively: Claude Code (a global skill) and Codex Desktop / CLI / IDE (a native global skill of its own).
Four Layers
- NotebookLM → Obsidian. Programmatic control of NotebookLM through
notebooklm-pyas a library (not the CLI — strictly one-shot, no retry duplication). Deep/fast research, source management, dedup, note extraction, and atomization into the vault. - .docx → Obsidian. Import from Google Drive (rclone) → parse → atomize → write.
- LLM Wiki. A compiled wiki on top of the atomic notes: it accumulates through an explicit
merge (not RAG, not a recompute on every query), linked with
[[wikilinks]]. - FTS5 memory. A local full-text index of the whole vault on stdlib SQLite, bm25 + snippets, auto-updates after every write. Search for agents.
Installation
git clone https://github.com/howdeploy/ObsidianDataWeave.git
cd ObsidianDataWeave
bash install.sh --vault-path "/path/to/your/vault"
Or hand the agent this one line and it does the rest: "clone
https://github.com/howdeploy/ObsidianDataWeave.git and run bash install.sh --vault-path "/path/to/vault" in the cloned directory".
The installer checks for Python 3.10+, installs the dependencies (python-docx, pyyaml), and
creates a config.toml with the vault path. After installation the skill works from any directory.
| Mode | Flag | What it registers |
|---|---|---|
| claude (default) | --mode claude |
A global skill in ~/.claude/skills/obsidian-dataweave/ plus a block appended to ~/.claude/CLAUDE.md |
| codex | --mode codex |
A native global skill in ~/.agents/skills/obsidian-dataweave/ for Codex Desktop / CLI / IDE |
| local | --mode local |
Dependencies and config only |
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.
- 1mo ago First seen · 135 lines · 72 tokens per session scan A 566c8d6c5cfa
ObsidianDataWeave: NotebookLM, Atomization, and LLM Wiki is a skill published in the GitHub repository howdeploy/deploychan_mcp (17 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 1,849 once invoked, about $0.0003 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 skills, from other repositories
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
kb-lint
Health check for the PARA Knowledge Base. Detects orphan documents, broken links, index drift, tag issues, and stale content. Run periodically or as part of weekly review.
memento
Capture durable knowledge from the current work session into Memento Vault. Use when the user asks to remember, save, capture, or record decisions, discoveries, bug fixes, or reusable patterns.
inception
Run or preview Memento Vault consolidation. Use when the user asks to consolidate, find patterns, run inception, preview clusters, or synthesize cross-session themes.
Obsidian Automation
Automate Obsidian knowledge management, note linking, and personal knowledge base workflows.
refresh-context
A context snapshot updater for Core Context.md, a summary file built from nine main system files and selected essays. It refreshes that summary when the underlying material changes or the snapshot is more than 30 days old.