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 Hank95/mdpm --skill pm-sync-jiragit clone --depth 1 https://github.com/Hank95/mdpmWrote 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/hank95/mdpm/pm-sync-jira)<a href="https://agentmods.dev/skills/hank95/mdpm/pm-sync-jira"><img src="https://agentmods.dev/badge/skills/hank95/mdpm/pm-sync-jira.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.00013 | $0.01214 |
| Opus 5 | $0.00006 | $0.00607 |
| Sonnet 5 | $0.00003 | $0.00243 |
| Haiku 4.5 | $0.00001 | $0.00121 |
Grade A, and why
pm-sync-jira 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 6d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pm-sync-jira
Bridge MDPM tasks with Jira. Works only if a Jira MCP server is connected.
Argument $1: push (default), pull, or both.
push— send local state out to Jirapull— bring in newly assigned Jira issues as inbox itemsboth— pull first, then push
Steps
0. Detect the Jira MCP
Look for tools prefixed with something like mcp__jira__*, mcp__atlassian__*, mcp__*jira*__*, or any tool whose name clearly matches Jira (create_issue, update_issue, transition_issue, get_issue, search_issues, add_comment).
If no Jira MCP is available:
-
Do NOT fail. Instead, generate a copy/pasteable summary suitable for pasting into a Jira comment or ticket body:
Jira MCP not detected. Here's a summary you can paste into Jira: **Active:** - [PRJ-123] Title — <latest work log> Acceptance criteria progress: 3/5 **Completed today:** - [PRJ-120] Title — <what shipped> **Blockers:** - [PRJ-125] — needs <thing>, waiting on <person> -
Tell the user: "To enable automatic sync, install an Atlassian/Jira MCP server (e.g.
@modelcontextprotocol/server-atlassianor the official Atlassian MCP), register it in your.mcp.json, and rerun this command." -
Exit.
1. Load Jira config
Check .mdpm/config.json for:
jira.default_project— project key for new issues (e.g.ENG)jira.issue_type— default issue type (Task,Story,Bug)jira.status_map— map of MDPM status → Jira workflow transition name- Example default:
{"backlog": "To Do", "active": "In Progress", "blocked": "Blocked", "done": "Done"}
- Example default:
jira.priority_map— map of MDPM priority → Jira priority (default:{"high": "High", "medium": "Medium", "low": "Low"})jira.field_map— overrides
If config is missing, ask the user for the minimum needed (default_project) and offer to save it.
2. Push (default)
For each task in tasks/active/ and recently updated tasks/done/:
- If
jira_idis null: Create a new Jira issue via the available MCP tool. Field mapping:
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.
- 6d ago First seen · 115 lines · 13 tokens per session scan A 76e09511a0f4
pm-sync-jira is a skill published in the GitHub repository Hank95/mdpm (3 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 1,214 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 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.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).