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 borisvu/obsidian-vault-cowork-plugins --skill project-lifecyclegit 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/skills/borisvu/obsidian-vault-cowork-plugins/project-lifecycle)<a href="https://agentmods.dev/skills/borisvu/obsidian-vault-cowork-plugins/project-lifecycle"><img src="https://agentmods.dev/badge/skills/borisvu/obsidian-vault-cowork-plugins/project-lifecycle/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/borisvu/obsidian-vault-cowork-plugins/project-lifecycle"><img src="https://agentmods.dev/badge/skills/borisvu/obsidian-vault-cowork-plugins/project-lifecycle.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.00036 | $0.03495 |
| Opus 5 | $0.00018 | $0.01747 |
| Sonnet 5 | $0.00007 | $0.00699 |
| Haiku 4.5 | $0.00004 | $0.00349 |
Grade A, and why
project-lifecycle 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Lifecycle Skill
Detect stale projects, classify them for archiving, execute moves to PARA/4 Archive, and keep the CLAUDE.md Projects table in sync. Organized into numbered sections that commands reference directly.
Section 1: Core Concepts
Definitions
| Term | Meaning |
|---|---|
| Project | A folder in PARA/1 Projects/ representing active work (may contain sub-folders and notes) |
| Umbrella project | A project folder that contains sub-project folders (e.g., Data Management contains Data copy, Related Tables) |
| Sub-project | A folder nested inside an umbrella project |
| Staleness | A project with no recent diary mentions, no recent Jira activity, and/or a terminal Jira status |
| Archive | Moving a project folder to PARA/4 Archive/Archive {YYYY}/ — the project is preserved but no longer active |
| Resources | Moving a project folder to PARA/3 Resources/ — the content is reference material, not project work |
Archive Location
PARA/4 Archive/
├── Archive 2025/
│ ├── PROJECT-4585/ ← standalone project
│ └── PROJECT-6599 - Bug empty fields/ ← standalone project
└── Archive 2026/
├── Data Management/ ← parent umbrella preserved
│ ├── Calculating Simple... PROJECT-5984/
│ └── Creating Database Schemas.../
└── PROJECT-6837 - Bug.../ ← standalone project
Work Week
Sunday through Thursday (Israel). Friday and Saturday are non-work days. Use ~~time MCP for the current date — never guess.
Section 2: Inventory Rules
Scanning PARA/1 Projects/
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 · 343 lines · 36 tokens per session scan A e85219773aaf
project-lifecycle is a skill published in the GitHub repository borisvu/obsidian-vault-cowork-plugins (4 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 3,495 once invoked, about $0.0002 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.