capture

capture is a command for coding agents from Michael-OvO/obsidian-knowledge-agent. It costs 25 tokens per session (363 once invoked), scanned A, original, MIT.

A quick note-saving command for an Obsidian vault, a folder of linked notes stored as files. It places a link, thought, article, or code snippet into one clean note using the vault’s existing organization.

In plain words
What is it for?
Use it to capture URLs, thoughts, articles, and snippets into the best-fit folder, or into an Inbox when the right location is unclear.
Why use it?
It keeps small pieces of information from becoming scattered or over-engineered notes. It also preserves the source link and adds only light metadata and relevant connections.

Command

Part of the obsidian-knowledge plugin — 1 skill, 12 commands, 2 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/michael-ovo/obsidian-knowledge-agent/capture
Clone the repo
git clone --depth 1 https://github.com/Michael-OvO/obsidian-knowledge-agent

Or install obsidian-knowledge, the plugin that ships this one along with the rest of its 1 skill, 12 commands, 2 hooks.

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 capture

README.md
[![agentmods](https://agentmods.dev/badge/commands/michael-ovo/obsidian-knowledge-agent/capture.svg)](https://agentmods.dev/commands/michael-ovo/obsidian-knowledge-agent/capture)
Your own site
<a href="https://agentmods.dev/commands/michael-ovo/obsidian-knowledge-agent/capture"><img src="https://agentmods.dev/badge/commands/michael-ovo/obsidian-knowledge-agent/capture.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 363 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00025 $0.00363
Opus 5 $0.00013 $0.00181
Sonnet 5 $0.00005 $0.00073
Haiku 4.5 $0.00003 $0.00036

Measured 5d ago against content hash c609fae3ea02, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

capture 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 5d 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.

plugins/obsidian-knowledge/commands/capture.md · 25 lines

What it actually says

Save this as one clean note. Keep it light — this is a Capture, not a full build.

If this folder isn't a vault yet (no .agents/ and no notes), still save the note in place — then mention that /obsidian-knowledge:setup would give it a proper home.

  1. Recall + fit. Glance at .agents/learned/conventions.md if it exists, and at how this vault is already organized, so the note lands in the right folder with matching naming and frontmatter.
  2. Make the note. One well-titled note: a short, natural body (a sentence or two is fine), minimal frontmatter (tags, created, and a source if there is one), and a wikilink to anything obviously related. No scaffold, no index, no canvas.
    • If I gave you a URL, fetch it and write a tight summary plus the link.
    • If I gave you a thought or snippet, capture it faithfully, lightly cleaned up.
  3. Place it in the best-fit existing folder — or leave it in Inbox/ if nothing fits and you're unsure — and tell me where it went.
  4. Reflect only if there's a real lesson (e.g. a new filing preference); otherwise a one-line journal entry is plenty. Don't over-ceremony a quick capture.

$ARGUMENTS

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. 5d ago First seen · 25 lines · 25 tokens per session scan A c609fae3ea02

Subscribe to this mod's changes

capture is a command published in the GitHub repository Michael-OvO/obsidian-knowledge-agent (207 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 363 once invoked, about $0.0001 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.

Related

Other commands, from other repositories