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 wei63w/pm-manager --skill pm-nextgit clone --depth 1 https://github.com/wei63w/pm-managerWrote 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/wei63w/pm-manager/pm-next)<a href="https://agentmods.dev/skills/wei63w/pm-manager/pm-next"><img src="https://agentmods.dev/badge/skills/wei63w/pm-manager/pm-next/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/wei63w/pm-manager/pm-next"><img src="https://agentmods.dev/badge/skills/wei63w/pm-manager/pm-next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00516 |
| Opus 5.5 | $0.00006 | $0.00206 |
| Sonnet 5.5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
pm-next 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.
What it actually says
User Input
$ARGUMENTS
Optional: --peek (do not mark in_progress).
Outline
- Require init. Read
state/todo.md. - Pick the first open/in_progress item ordered by blocking>high, then P0>P1 (no 3-item cap).
- Unless
--peek, set statusin_progressin state + module mirror. - Print task, evidence link, suggested action; remind
/pm-done TODO-id.
Shared Workflow (all /pm-* commands)
Follow this order when the command mutates .pm/ state:
- Read
.pm/config/project.yamland.pm/config/local.yaml(if missing and command is not init → recommend/pm-init). - If
.pm/metadata is valid, load it; do not force a full-repo rescan. On-demand incremental scan usingsources+extra_scan_roots+--path+ conversation paste (highest priority for/pm-fix). Prefer.pm/architecture/map.jsonand the document index before walking the tree. - Desensitize evidence →
.pm/evidence/scans/{command}-{timestamp}.json(secrets →***). Never persist raw secrets. - Optional charter compare only when
charter.status == approved(attachconfidence). Draft PRD/charter MUST NOT be used as the baseline. - Incremental merge into module
findings.md/todo.md; sync authoritativestate/todo.md. - Refresh
state/overview.mdwith all open/in_progress blocking+high todos (no 3-item cap). Medium/low: counts only unless--verbose. - Append audit to
.pm/state/audit.jsonl(command, time, input/output summary; include reasoning when the step was AI-produced). - Output risk summary + recommended next step (≤20 lines). Never auto-write source/SQL/cloud or land generated docs/rules without explicit user confirmation.
- Closing:
templates/commands/_closing.md轻量档。中文摘要。
Design baseline: docs/prd.md + 宪章。
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 · 41 lines · 14 tokens per session scan A 65cbc6b7671a
pm-next is a skill published in the GitHub repository wei63w/pm-manager (87 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 516 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-30.
Other skills, from other repositories
ledger-tasks-yylo
Durable in-repo task state for coding agents — Kanban tasks with stable IDs, evidence-backed status marks, blocked-by dependencies, and next-ready selection. Use when starting, selecting, sequencing, or closing implementation tasks for a coding-agent project.
meeting-notes-to-tasks
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
task-decomposition
Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.
citruscoastai
Guides agents to engage and transact with citruscoastai, an AI venture-operator agent, when they need hired AI labor or an agent-to-agent collaborator.
outlook-calendar
A skill for managing Microsoft Outlook and Microsoft 365 calendar events through a connected account.
cron
Use this skill only for scheduled or recurring tasks. Manage jobs with qwenpaw cron list/create/get/state/pause/resume/delete/run, and always pass --agent-id explicitly.