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-inboxgit 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-inbox)<a href="https://agentmods.dev/skills/hank95/mdpm/pm-inbox"><img src="https://agentmods.dev/badge/skills/hank95/mdpm/pm-inbox/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/hank95/mdpm/pm-inbox"><img src="https://agentmods.dev/badge/skills/hank95/mdpm/pm-inbox.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.00014 | $0.00752 |
| Opus 5.5 | $0.00006 | $0.00301 |
| Sonnet 5.5 | $0.00003 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
pm-inbox 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pm-inbox
Walk through tasks/inbox/ one item at a time and decide what to do with each.
Steps
-
List inbox contents.
- If
tasks/inbox/is empty or missing, say so and exit. Optionally, offer to pull new items from Jira/Wrike via/pm-sync-jiraor/pm-sync-wrike.
- If
-
Sort inbox by
createddate ascending (oldest first — stop things from rotting). -
For each item, show this summary to the user:
## Inbox item 1 of N: [PRJ-INBOX-003] Short title Source: <from jira_id or wrike_id if present, else "direct"> Created: YYYY-MM-DD <Objective section, truncated to ~3 lines> **Triage options:** a) Accept → move to backlog (set priority, tags, due) b) Start now → move directly to active c) Plan → run /pm-plan to decompose d) Reject → delete (or archive if synced to Jira/Wrike) e) Snooze → leave in inbox, move on f) Delegate → set assigned_to and leave in backlog -
Process the user's choice:
- Accept: Ask for priority (default medium), tags, optional due date. Update frontmatter. Assign a real task ID (replace any
PRJ-INBOX-*placeholder with the next sequentialPRJ-XXX). Rename the file to<new-id>-<slug>.mdto match the MDPM filename convention. Move totasks/backlog/. - Start now: Same as Accept (including the filename rename), but move to
tasks/active/and setstatus: active. Append work log entry: "Triaged from inbox, started work." - Plan: Keep the inbox file in place, invoke
/pm-planlogic on its contents. After planning, move the original inbox item todone/with a work log entry "Replaced by decomposition into PRJ-XXX, PRJ-YYY." - Reject: Confirm with the user. If the task has a
jira_idorwrike_id, offer to close it in the external system via sync. Then delete the file (inbox is the ONLY directory where deletion is allowed). - Snooze: No change. Move to next item.
- Delegate: Ask for assignee name, set
assigned_to, move totasks/backlog/.
- Accept: Ask for priority (default medium), tags, optional due date. Update frontmatter. Assign a real task ID (replace any
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.
- 1mo ago First seen · 58 lines · 14 tokens per session scan A 6a71df604243
pm-inbox is a skill published in the GitHub repository Hank95/mdpm (3 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 752 once invoked, about $0.0001 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
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.
submission
This skill should be used when the user asks to "write a query letter", "query", "querying", "pitch", "blurb", "back cover copy", "jacket copy", "comp titles", "comparable titles", "synopsis for agents", "submit to agents", "submission tracker", "self-publishing description", "retailer description", "ready to query"…
kaneo-cli
Work with Kaneo tasks, projects, comments and time tracking through the kaneo CLI. Use when the user asks to list, create, update, assign or close Kaneo tasks, see what is assigned to them, comment, log time, or script against a Kaneo workspace on Kaneo Cloud or a self-hosted instance.
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.
stale-ticket-triage
Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.