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/borisvu/obsidian-vault-cowork-pluginsWrote 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/triage)<a href="https://agentmods.dev/commands/borisvu/obsidian-vault-cowork-plugins/triage"><img src="https://agentmods.dev/badge/commands/borisvu/obsidian-vault-cowork-plugins/triage/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/borisvu/obsidian-vault-cowork-plugins/triage"><img src="https://agentmods.dev/badge/commands/borisvu/obsidian-vault-cowork-plugins/triage.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.00014 | $0.00792 |
| Opus 5 | $0.00007 | $0.00396 |
| Sonnet 5 | $0.00003 | $0.00158 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
triage 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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Command
Scan PARA/0 Inbox/, classify each file by content and quality, detect conflicts with existing vault notes, and execute confirmed actions.
Always shows a plan and asks for confirmation. No files are deleted or moved without explicit user approval.
Usage
/para-flow:triage → scan, classify, present plan, ask to proceed
Instructions
Step 0: Get Time
Use ~~time MCP to get the current date, time, and day of week (inbox-triage skill Section 1).
Step 1: Inventory
Use inbox-triage skill Section 2 (Inventory Rules).
List all files in PARA/0 Inbox/. For each file:
- Read full content (not just frontmatter)
- Record: filename, has_frontmatter, frontmatter_fields, content_length, content_preview
If the inbox is empty, print "Inbox is empty. Nothing to triage." and exit.
List non-markdown files separately if any are found. Treat nested folders as single items.
Step 2: Classify
Use inbox-triage skill Section 3 (Classification Rules).
Classify each file as DELETE or MOVE:
- DELETE: empty, single URL, stub, fewer than 3 meaningful lines
- MOVE: everything with value — sub-classify by content type (Person, Jira, Term, Project material, Reference, Meeting note)
Apply the safety rule: files with 10+ lines of meaningful content are never DELETE.
Step 3: Conflict Check
Use inbox-triage skill Section 4 (Conflict Detection).
For each MOVE candidate, search for existing vault notes using deterministic signals:
- Exact filename match in PARA (excluding Inbox and Archive)
- Jira key match in Projects and Resources/Jira
- Person name match in Areas/People
- Alias match in vault frontmatter
Annotate conflicts on the MOVE items.
Step 4: Present Plan
Use inbox-triage skill Section 5 (Presentation Format).
Display three grouped tables:
- DELETE table (empty/temporary files with reasons)
- MOVE table (files with type, target, and planned enhancement)
- CONFLICT table (MOVE items that match existing vault notes)
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.
- 9d ago First seen · 97 lines · 14 tokens per session scan A 470edfce456d
triage 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 14 tokens to every session and 792 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
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.