Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add borisvu/obsidian-vault-cowork-plugins/plugin install para-flowWrote 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/borisvu/obsidian-vault-cowork-plugins/start)<a href="https://agentmods.dev/commands/borisvu/obsidian-vault-cowork-plugins/start"><img src="https://agentmods.dev/badge/commands/borisvu/obsidian-vault-cowork-plugins/start.svg" alt="Measured on agentmods" 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.00009 | $0.00761 |
| Opus 5 | $0.00005 | $0.00380 |
| Sonnet 5 | $0.00002 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
start 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 6d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Command
See CONNECTORS.md for tool references.
Initialize task and memory systems within an existing PARA-based Obsidian vault, then open the dashboard.
Instructions
1. Verify Vault Structure
Confirm the working directory is an Obsidian vault by checking for:
./PARA/directory with expected subdirectories./Work Diary/directory
If these don't exist, STOP and tell the user: "This doesn't look like your Work Notes vault. Please run this from the vault root directory."
2. Check What Exists
Check the vault root for:
CLAUDE.md— working memory hot cachedashboard.html— visual dashboard
3. Create What's Missing
If dashboard.html doesn't exist: Copy from ${CLAUDE_PLUGIN_ROOT}/skills/dashboard.html to vault root.
If CLAUDE.md doesn't exist: This is a fresh setup — after opening the dashboard, begin the memory bootstrap (step 5).
4. Open the Dashboard
Tell the user: "Dashboard is ready at dashboard.html. Open it from your file browser to get started."
5. Orient the User
If everything was already initialized:
Dashboard open. Your tasks and memory are loaded.
- /para-flow:update to sync tasks and check memory
- /para-flow:update --comprehensive for a deep scan
- /para-flow:standup for today's standup report
If memory hasn't been bootstrapped yet, continue to step 6.
6. Bootstrap Memory (First Run Only)
Only if CLAUDE.md doesn't exist.
Scan existing PARA content to populate CLAUDE.md:
- People: Read filenames and frontmatter from
PARA/2 Areas/People/ - Partners/Customers: Read from
PARA/2 Areas/Partners/andPARA/2 Areas/Customers/ - Projects: Recursively read from
PARA/1 Projects/— projects may be subdirectories containing multiple notes - Terms: Read individual files from
PARA/3 Resources/Terms/(each file is one term)
Ask the user about anything that can't be decoded from existing vault content:
I found some terms in your tasks and notes I want to confirm:
1. **PSR** — What does this stand for?
2. **John Z** — Is this John Smith from People/?
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.
- 6d ago First seen · 102 lines · 9 tokens per session scan A 1fa595543c99
start is a command published in the GitHub repository borisvu/obsidian-vault-cowork-plugins (4 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 761 once invoked, about $0.0000 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.