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.
git 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/commands/ethanaubuchon/dossier-tradecraft/dossier)<a href="https://agentmods.dev/commands/ethanaubuchon/dossier-tradecraft/dossier"><img src="https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/dossier/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/commands/ethanaubuchon/dossier-tradecraft/dossier"><img src="https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/dossier.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.00020 | $0.00275 |
| Opus 5 | $0.00010 | $0.00138 |
| Sonnet 5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
dossier 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.
What it actually says
You are starting a session that needs Dossier vault context. The user's task (if any): $ARGUMENTS
This is the /dossier recipe of the dossier-tradecraft framework — a thin enforcement command. Its only job is to ensure the profile-load step runs before any other action.
Workflow
-
Load context. Invoke the
load-contextskill. This loadsprofile.mdviamcp__dossier-mcp__get_vault_contextand runs the profile's session-start conventions (e.g., inbox nudge if non-empty). -
Branch on
$ARGUMENTS:- Empty: Briefly acknowledge that vault context is loaded. Wait for the user's next instruction.
- Non-empty: Process the task with profile context now in scope. Honor any session-start conventions surfaced by
load-context(e.g., if the inbox nudge fires, mention it inline as you proceed).
Why this exists
Multi-part prompts like "connect to dossier and do X" routinely cause the profile-load step to be skipped — the agent jumps to the task and never calls get_vault_context. This recipe forces the order: load first, act second.
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 · 20 lines · 20 tokens per session scan A ce9b1e5ed8ab
dossier is a command published in the GitHub repository ethanaubuchon/dossier-tradecraft (3 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 275 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-31.
Other commands, from other repositories
session-learn
Extract knowledge from the current session. Invoke with /session-learn or "extract this session".
help
Show everything the Obsidian Knowledge Agent can do, with every command and an example.
capture
Quickly save something as a single clean note in the right place — a link, a thought, an article, a snippet.
reflect
Reflect on recent work — log lessons to the journal and propose distilled rule updates for review.
flow-import
Cold-start import — extract baseline knowledge from an existing project (resumable).
knowledge
Knowledge base utilities — sync (pull/push), lint, stats, decay.