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 musingfox/cc-plugins/plugin install obwWrote 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/musingfox/cc-plugins/pm)<a href="https://agentmods.dev/skills/musingfox/cc-plugins/pm"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/pm/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/musingfox/cc-plugins/pm"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/pm.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.00086 | $0.02289 |
| Opus 5.5 | $0.00034 | $0.00916 |
| Sonnet 5.5 | $0.00017 | $0.00458 |
| Haiku 4.5 | $0.00009 | $0.00229 |
Grade A, and why
pm 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 10d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pm — Obsidian Project Management
Run the obsidian CLI directly — no sub-agent. Before any CLI call, invoke the obsidian:obsidian-cli skill to load exact syntax — never run obsidian help/--help to discover it. This skill owns only the PM conventions: folder layout, template names, property schema, and dashboard generation.
CLI gotcha: file= resolves like a wikilink — bare note name only, no path, no .md. Use path= for vault-root-relative paths. If a command returns File not found after a create, fix the parameter — never re-run create (it makes name 1.md duplicates).
property:set gotcha: one property per call, no batch form. Pass type=list for tags, type=date for due/completed — omit type= and it's stored as plain text.
Config (.obsidian.yaml)
vault: <VAULT_NAME>
pm:
project: <PROJECT_NAME>
Missing config or pm.project → tell the user to run /obw:init and stop. Never guess the vault.
Vault Layout
pm/
├── {project}/
│ ├── dashboard.base # project dashboard
│ ├── tasks/ # active tasks
│ │ └── archive/ # completed tasks
│ └── docs/ # docs
└── dashboard.base # cross-project dashboard (optional)
Every project has all three: tasks/, docs/, dashboard.base. /obw:init bootstraps them. If a pm operation finds pm/{project}/dashboard.base missing, regenerate it (see Dashboards) before reporting done.
Beyond that, folders are created on demand — create / move auto-create missing parent folders. No mkdir needed.
Filenames
Kebab-case, always: lowercase, whitespace and punctuation → -, collapse repeats, Unicode characters kept intact. Same rule as /obw:jot note mode.
The human-readable title is not derivable from the filename, so it lives in the title property. Obsidian's {{title}} resolves to the filename, so the H1 stays kebab — title is what dashboards display.
Implement Auth→pm/{project}/tasks/implement-auth.md,title: Implement Auth
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed · -21 lines · +2 tokens per session 331dd651ef39
- 25d ago Changed · +9 lines b3f88832964a
- 1mo ago Changed · +24 lines · +7 tokens per session 1ff059cd05c0
- 1mo ago Changed · +25 lines 9a555e831a60
- 1mo ago First seen · 93 lines · 77 tokens per session scan A 1ebcf9516afe
pm is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 2,289 once invoked, about $0.0003 per session on Opus 5.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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…