A command for exporting a redacted project-governance summary as Markdown. Redaction removes secrets and other sensitive details before the file is shared.

Use it to export audit notes, reviews, test gaps, safeguards, and architecture paths from the project's governance data.

It creates a shareable project snapshot without exposing credentials, private keys, local configuration, or raw logs.

export — Command by wei63w

Install

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.

agentmods

npx agentmods add commands/wei63w/pm-manager/export

Clone the repo

git clone --depth 1 https://github.com/wei63w/pm-manager

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 569 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00013	$0.00569
Opus 5	$0.00006	$0.00284
Sonnet 5	$0.00003	$0.00114
Haiku 4.5	$0.00001	$0.00057

Measured 2d ago against content hash 6b431b2744a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

export 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 2d 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.

Origin

This is a copy

100% identical to pm-export — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/pm-manager/templates/commands/export.md · 34 lines

How it starts

The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

Outline

Prefer pm export from the project root (--from / --to / --out，可选 --with-diagrams)。Default output: .pm/exports/pm-export-YYYYMMDD.md。
The file must include: audit window, dialogue notes, snapshot excerpt, reviews table, test-gaps, guard, and architecture paths (embed .mmd only with --with-diagrams). If the CLI is unavailable, assemble the same sections and redact before writing. If residue remains (AKIA…, BEGIN PRIVATE KEY), delete the file and fail.
Exclude local.yaml, credentials, raw logs, secret originals. Never include un-redacted secrets.
Show the export path and ask the user to open it.

Shared Workflow (all /pm-* commands)

Follow this order when the command mutates .pm/ state:

Read .pm/config/project.yaml and .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 using sources + extra_scan_roots + --path + conversation paste (highest priority for /pm-fix). Prefer .pm/architecture/map.json and 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 (attach confidence). Draft PRD/charter MUST NOT be used as the baseline.
Incremental merge into module findings.md / todo.md; sync authoritative state/todo.md.
Refresh state/overview.md with 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: _closing.md 完整档（只列已写出的导出文件）。

Read the full file on GitHub · 34 lines

Changes

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.

2d ago First seen · 34 lines · 13 tokens per session scan A 6b431b2744a5

Subscribe to this mod's changes

export is a command published in the GitHub repository wei63w/pm-manager (96 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 569 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pm-export, differing in 0 lines, and is treated as a copy.

Planning Project Management Project management Testing agent-skills ai-agents claude-code cursor skills

export

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

User Input

Outline

Shared Workflow (all /pm-* commands)

What this file has done since we first saw it

Other commands, from other repositories

webperf

spec

install

audit-rules

search

index