Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mrDesign-ww/vault-osnpx agentmods add skills/mrdesign-ww/vault-os/pm-skillsWrote 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/mrdesign-ww/vault-os/pm-skills)<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/pm-skills"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/pm-skills/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/mrdesign-ww/vault-os/pm-skills"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/pm-skills.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.00179 | $0.02564 |
| Opus 5 | $0.00089 | $0.01282 |
| Sonnet 5 | $0.00036 | $0.00513 |
| Haiku 4.5 | $0.00018 | $0.00256 |
Grade A, and why
pm-skills 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Management — Domain Orchestrator & Delivery Loop
This orchestrator does two jobs. Routing: fork context, classify a PM inquiry with
scripts/pm_goal_router.py, run exactly one of the 8 sub-skills, return a digest.
Looping: turn a delivery goal into a bounded agentic loop — pull live Jira data via the
bundled Atlassian MCP, bridge it into the domain's deterministic analytics tools, verify
every step with machine-run gates, and refuse to close until everything is verified or a
human waives it. The bundled .mcp.json wires the Atlassian Remote MCP
(https://mcp.atlassian.com/v1/sse, OAuth handled by Claude Code).
When to invoke
| Symptom | Sub-skill |
|---|---|
| "Project/portfolio health, risk EMV, capacity" | senior-pm |
| "Sprint velocity, retro follow-through, ceremony health, when-will-it-be-done" | scrum-master |
| "JQL, Jira workflows, boards, automation" | jira-expert |
| "Confluence spaces, page trees, content audits" | confluence-expert |
| "Users, groups, permissions, SSO" | atlassian-admin |
| "Reusable Jira/Confluence templates" | atlassian-templates |
| "Meeting transcripts, talk time, action items" | meeting-analyzer |
| "Status updates, 3P updates, stakeholder comms" | team-communications |
Routing logic (deterministic)
Run the router — do not eyeball the table when a script can decide:
python3 scripts/pm_goal_router.py --text "<the goal>" --output json
Exit 0 → route_to names the sub-skill: load its SKILL.md and follow its workflow.
Exit 2 → ask ONE clarifying question naming the listed candidates, with a recommended
answer. Exit 3 → no signal: ask the user to restate the goal with the deliverable named.
Never guess silently; never silently chain a second sub-skill — digest first, confirm, then
chain.
The delivery loop (agentic)
For goals (not questions) — "get sprint 14 to a verified close", "produce a portfolio health report from live Jira", "make our flow metrics visible weekly" — run the loop-library contract (Observe → Choose → Act → Verify → Record → Repeat-or-stop):
What ships with it
8 files 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.
- assets/expected_flow_metrics.json 1021 B
- assets/sample_jira_snapshot.json 4.5 KB
- references/agentic_delivery_governance.md 4.2 KB
- references/flow_forecasting_canon.md 3.9 KB
- references/pm_loop_playbook.md 4.7 KB
- scripts/delivery_loop_gate.py 7.3 KB runs code
- scripts/jira_snapshot_bridge.py 12 KB runs code
- scripts/pm_goal_router.py 6.7 KB runs code
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 First seen · 174 lines · 179 tokens per session scan A 92318bad0543
pm-skills is a skill published in the GitHub repository mrDesign-ww/vault-os (2 stars, last pushed 3d ago), licensed MIT. It adds 179 tokens to every session and 2,564 once invoked, about $0.0009 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
project-manager
This skill has been upgraded with agentic AI capabilities, OKR/KPI integration patterns, and async-first workflows based on 2026 PM best practices research.
scrumboy-board-operator
Operate Scrumboy projects and boards through MCP or Agoragentic APIs. Use when an agent needs to inspect board state, plan sprint work, create todos, move cards, manage tags, or summarize project health.
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
atls
A command-line tool for working with Atlassian Jira, Confluence, and Bitbucket Server or Data Center. It includes rules for searching, reading, comparing, editing, and safely publishing Atlassian content.
Jira Automation
Automate Jira project management workflows, sprint planning, issue tracking, and reporting.
jira
Use when the user asks about Jira work — boards, sprints, backlog, epics, issues, JQL search, creating/updating/transitions, comments, worklogs — or when the jira MCP server is not yet configured and needs setup. Covers the jira-mcp MCP server (43 tools) for Jira Cloud and Data Center.