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-wrikegit 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-wrike)<a href="https://agentmods.dev/skills/hank95/mdpm/pm-sync-wrike"><img src="https://agentmods.dev/badge/skills/hank95/mdpm/pm-sync-wrike.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.00014 | $0.00951 |
| Opus 5 | $0.00007 | $0.00476 |
| Sonnet 5 | $0.00003 | $0.00190 |
| Haiku 4.5 | $0.00001 | $0.00095 |
Grade A, and why
pm-sync-wrike 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 7d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pm-sync-wrike
Bridge MDPM tasks with Wrike. Works only if a Wrike MCP server is connected.
Argument $1: push (default), pull, or both.
push— send local state out to Wrikepull— bring in newly assigned Wrike tasks as inbox itemsboth— pull first, then push
Steps
0. Detect the Wrike MCP
Look for tools prefixed with something like mcp__wrike__*, mcp__*wrike*__*, or any tool whose name clearly matches Wrike (create_task, update_task, get_folder, etc.).
If no Wrike MCP is available:
-
Do NOT fail. Instead, generate a copy/pasteable summary:
Wrike MCP not detected. Here's a standup-style summary you can paste directly: **Active:** - [PRJ-123] Title — <latest work log> **Completed today:** - [PRJ-120] Title — <what shipped> **Blockers:** - [PRJ-125] needs <thing> -
Tell the user how to enable: "Install a Wrike MCP server (https://github.com/modelcontextprotocol/servers or similar), add its config to
.mcp.json, and rerun this command." -
Exit.
1. Load Wrike config
Check .mdpm/config.json for:
wrike.folder_id— where to create new taskswrike.status_map— map of MDPM status → Wrike custom status namewrike.field_map— any overrides to the default field mapping
If the config is missing, ask the user for the minimum (folder_id) and offer to save it.
2. Push (default)
For each task in tasks/active/ and recently updated tasks/done/:
-
If
wrike_idis null: Create a new Wrike task using whatever MCP tool is available. Map fields:title→ Wrike title- Objective + Acceptance Criteria → description
priority→ Wrike priority (High/Normal/Low)tags→ Wrike tagsdue→ Wrike due dateassigned_to→ Wrike assignee (best-effort name match)- Status → Wrike status per
status_mapStore the returned Wrike ID back into the task file'swrike_id:frontmatter.
-
If
wrike_idexists: Update the Wrike task:- Transition status if changed
- Post new work log entries as Wrike comments (only entries newer than the last sync timestamp)
- Update due date, assignee, priority if changed
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.
- 7d ago First seen · 100 lines · 14 tokens per session scan A 259981d725a0
pm-sync-wrike is a skill published in the GitHub repository Hank95/mdpm (3 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 951 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).