capture-to-vault

capture-to-vault is a skill for Claude Code, Codex from ethanaubuchon/dossier-tradecraft. It costs 72 tokens per session (1,274 once invoked), scanned A, original, MIT.

A workflow that drafts and saves a research finding, decision, or synthesis as a note in a shared knowledge vault.

In plain words
What is it for?
Use it during research or planning to create a new vault note or update an existing one with conclusions, related notes, and citations.
Why use it?
It preserves useful research in an organized place so it can be refined and reused later, including its sources.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it during research or planning to create a new vault note or update an existing one with conclusions, related notes, and citations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ethanaubuchon/dossier-tradecraft/capture-to-vault
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.

Any agent
npx skills add ethanaubuchon/dossier-tradecraft --skill capture-to-vault
Clone the repo
git clone --depth 1 https://github.com/ethanaubuchon/dossier-tradecraft

Made for: Claude Code, Codex.

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-to-vault

README.md
[![agentmods](https://agentmods.dev/badge/skills/ethanaubuchon/dossier-tradecraft/capture-to-vault/github.svg)](https://agentmods.dev/skills/ethanaubuchon/dossier-tradecraft/capture-to-vault)
Your own site
<a href="https://agentmods.dev/skills/ethanaubuchon/dossier-tradecraft/capture-to-vault"><img src="https://agentmods.dev/badge/skills/ethanaubuchon/dossier-tradecraft/capture-to-vault/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 capture-to-vault

Your own site · 80×15
<a href="https://agentmods.dev/skills/ethanaubuchon/dossier-tradecraft/capture-to-vault"><img src="https://agentmods.dev/badge/skills/ethanaubuchon/dossier-tradecraft/capture-to-vault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,274 The whole file, excluding the scripts and references it only reads on demand.
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.00072 $0.01274
Opus 5.5 $0.00029 $0.00510
Sonnet 5.5 $0.00014 $0.00255
Haiku 4.5 $0.00007 $0.00127

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

Security

Grade A, and why

capture-to-vault 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.

skills/capture-to-vault/SKILL.md · 81 lines

How it starts

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

Capture to Vault

Draft a note and write it. Surface the slug and any non-obvious placement decisions afterward so the user can redirect or revise. Do not wait for approval before writing. One note per call.

Modes

  • create (default) — write a new vault note via mcp__dossier-mcp__create_note.
  • update — refine an existing note in place via mcp__dossier-mcp__update_note. Preserves required frontmatter and auto-bumps the updated: field.

Input

  • mode (optional) — create (default) or update.
  • body — the finding, decision, or synthesis. Markdown. Lead with the conclusion or key takeaway. In update mode, this represents the intended new state of the body (or a description sufficient to derive it from the loaded current state).
  • slug (required for update mode) — the existing note's slug.
  • related (optional) — vault slugs the note references. If absent, infer from body content and recent session context.
  • citations (optional) — list of {title, url, accessed} entries from web-researcher findings. Include whenever the body draws on web sources.
  • parent_slug (optional, create mode only) — path prefix hint, e.g. projects/relocation. If absent, infer from content and vault structure. Ignored in update mode.

Process — create mode

  1. Draft the destination slug.

    • If parent_slug is supplied: <parent_slug>/<topic-slug>.
    • Else: infer from body content and related notes. Place as a sibling to the most relevant related note. Avoid inbox/ unless nothing better fits.
  2. Draft the frontmatter:

    • title — readable title derived from the body's main claim
    • date — today's date (YYYY-MM-DD)
    • tags — 2–4 tags inferred from body
    • related — the input related (or inferred list)
  3. Draft the body. Ensure:

    • Lead with the conclusion or key takeaway
    • Density over readability — pack in conclusions and reasoning, not just facts
    • Self-contained — key context inline, not only via links
    • If citations present: include a ## Sources section at the end listing each citation (title — URL — accessed date)

Read the full file on GitHub · 81 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 · 81 lines · 72 tokens per session scan A 14d31cbb1d4e

Subscribe to this mod's changes

capture-to-vault is a skill published in the GitHub repository ethanaubuchon/dossier-tradecraft (3 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 1,274 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-31.