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 skills add ethanaubuchon/dossier-tradecraft --skill capture-to-vaultgit clone --depth 1 https://github.com/ethanaubuchon/dossier-tradecraftWrote 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/ethanaubuchon/dossier-tradecraft/capture-to-vault)<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.
<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>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.01274 |
| Opus 5 | $0.00036 | $0.00637 |
| Sonnet 5 | $0.00014 | $0.00255 |
| Haiku 4.5 | $0.00007 | $0.00127 |
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 12d 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 — 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 theupdated:field.
Input
mode(optional) —create(default) orupdate.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
-
Draft the destination slug.
- If
parent_slugis 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.
- If
-
Draft the frontmatter:
title— readable title derived from the body's main claimdate— today's date (YYYY-MM-DD)tags— 2–4 tags inferred from bodyrelated— the inputrelated(or inferred list)
-
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
citationspresent: include a## Sourcessection at the end listing each citation (title — URL — accessed date)
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.
- 12d ago First seen · 81 lines · 72 tokens per session scan A 14d31cbb1d4e
capture-to-vault is a skill published in the GitHub repository ethanaubuchon/dossier-tradecraft (3 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,274 once invoked, about $0.0004 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-31.
Other skills, from other repositories
self-improve
Extract lessons from the current session, or sweep the project's past sessions when asked, and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "distill past sessions", "sweep past…
recall-reasoning
Recall the reasoning behind a past change by locating the Claude Code transcript that produced it. Use when the user asks to "recall reasoning", "find reasoning", "look up reasoning", "recall implementation reasoning", "find the rationale", "why did I do X", "recall from transcripts", or "find the transcript for this…
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…
obsidian-memory
Cross-project long-term memory over an Obsidian brain vault: recall relevant notes before a task, and persist distilled conclusions (decisions, pitfalls, solutions, progress) back after a task. The vault is an optional aggregation/projection layer — repo-local artifacts stay the per-project source of truth, and sync…
raytsystem-save
Stage a cited synthesis as a typed raytsystem DRAFT bundle and escaped preview. Use for SAVE, preserving a verified query answer, preparing a knowledge proposal, or creating a reviewable draft; never treat SAVE as canonical promotion or publication.
codebase-memory-mcp
Resolve canonical Git checkouts, index and verify codebase-memory-mcp graphs through the guarded CLI, and safely audit duplicate worktree caches. Use when a user mentions codebase memory MCP, searchgraph, tracepath, indexrepository, worktree indexes, or oversized graph caches.