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/archive)<a href="https://agentmods.dev/commands/borisvu/obsidian-vault-cowork-plugins/archive"><img src="https://agentmods.dev/badge/commands/borisvu/obsidian-vault-cowork-plugins/archive.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.00012 | $0.00868 |
| Opus 5 | $0.00006 | $0.00434 |
| Sonnet 5 | $0.00002 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
archive 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 8d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive Command
Scan PARA/1 Projects/ for stale projects, recommend archiving, and execute confirmed moves.
Always shows a plan and asks for confirmation. No files are moved without explicit user approval.
Usage
/para-flow:archive → scan, classify, present plan, ask to proceed
/para-flow:archive --since 90 → override staleness threshold (default: 30 days)
Instructions
Step 0: Parse Arguments and Get Time
- Parse the argument string:
--since N→ override the 30-day staleness threshold with N days (see project-lifecycle skill Section 5)- No arguments → use default 30-day threshold
- Use
~~timeMCP to get the current date, time, and day of week (project-lifecycle skill Section 1).
Step 1: Inventory
Use project-lifecycle skill Section 2 (Inventory Rules).
Scan PARA/1 Projects/ and build a registry of all projects, including:
- Folder names, Jira keys, parent/child relationships
- Frontmatter status and dates from main .md files
- Umbrella detection (has sub-project folders)
Step 2: Enrich from Diary
Use project-lifecycle skill Section 3 (Diary Enrichment).
For each project in the registry, search Work Diary/ for mentions of the project name and Jira key. Record the most recent mention date.
Step 3: Enrich from Jira
Use project-lifecycle skill Section 4 (Jira Enrichment).
For projects with Jira keys, query Atlassian MCP for current status, resolution, last update, and assignee. If MCP is unavailable, skip and log a warning.
Step 4: Classify
Use project-lifecycle skill Section 5 (Classification Rules).
Classify each project as ARCHIVE, REVIEW, or ACTIVE based on:
- Jira terminal statuses (Done/Closed/Merged → always ARCHIVE)
- Diary mention recency
- Frontmatter status
- CLAUDE.md annotations
--since Nthreshold override if provided
Apply the umbrella rule: never classify umbrellas directly, only sub-projects.
Step 5: Present Plan
Use project-lifecycle skill Section 7 (Presentation Format).
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.
- 8d ago First seen · 108 lines · 12 tokens per session scan A d8acd1a3d89f
archive 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 12 tokens to every session and 868 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.