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 agentmods add skills/wei63w/pm-manager/pm-donenpx skills add wei63w/pm-manager --skill pm-donegit 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-done)<a href="https://agentmods.dev/skills/wei63w/pm-manager/pm-done"><img src="https://agentmods.dev/badge/skills/wei63w/pm-manager/pm-done.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 | $0.00010 | $0.00575 |
| Opus 5 | $0.00005 | $0.00287 |
| Sonnet 5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
pm-done 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 5d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
--- description: Close a todo (TODO-xxx), sync completed.md, refresh overview. handoffs:
- label: Status agent: pm.status prompt: Refresh status after closing todo send: true
User Input
$ARGUMENTS
Usage: TODO-001 | TODO-001 --note "..." | TODO-001 --start (only in_progress).
Outline
- Parse TODO id. Require it exists in
state/todo.md. --start→in_progressonly.- Else →
done, append tostate/completed.mdand modulecompleted.md, remove/mark done in state todo. - If linked finding has no other open todos →
resolved. - Refresh overview; confirm the item is no longer in the open blocking/high list.
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轻量档（1–2 个已存在链接）。中文摘要。
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.
- 5d ago First seen · 47 lines · 10 tokens per session scan A 4e63c3812194
pm-done is a skill published in the GitHub repository wei63w/pm-manager (99 stars, last pushed 5d ago), licensed MIT. It adds 10 tokens to every session and 575 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-30.
Other skills, from other repositories
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
documentation-and-adrs
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
chinese-documentation
中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用，不要根据上下文自动触发。.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
skillshare-update-docs
Update website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all website/docs/ categories (commands, reference…