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-charternpx skills add wei63w/pm-manager --skill pm-chartergit 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-charter)<a href="https://agentmods.dev/skills/wei63w/pm-manager/pm-charter"><img src="https://agentmods.dev/badge/skills/wei63w/pm-manager/pm-charter.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.00026 | $0.00512 |
| Opus 5 | $0.00013 | $0.00256 |
| Sonnet 5 | $0.00005 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
pm-charter 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 6d 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
Subcommands: create | import <path> | discover | approve | skip.
Outline
If $ARGUMENTS is empty, do not guess a subcommand. Show this Chinese wizard and wait:
宪章还没选定动作。请回复其一：
- create — 按模板起草宪章（仍是草稿，须再 approve）
- import <路径> — 从已有文件导入
- discover — 扫描 charter_candidates（优先 Spec Kit）
- approve — 把宪章升为基线（若 PRD 仍是草稿，同时 confirm）
- skip — 不要宪章基线；技术扫描仍可用
Then:
discover: rescancharter_candidates(Spec Kit constitution first); map into.pm/charter/; updatesources.md.import: parse given path into charter files;source=imported.create: interactive fill from templates.approve:charter.status=approved. If.pm/prd/prd.mdis draft, also setprd.status=confirmed(same as/pm-init confirm).skip:charter.status=absent. If the user is skipping the generated PRD, setprd.status=skipped. Do not use skipped/draft charter to judge whether a demand is “reasonable”.- Any write →
needs_recompare=true. - Prefer
/pm-initfor first-time Spec Kit detection and PRD draft. This command is the charter lifecycle after that. approveis the only path that makes the charter a baseline. Technical/pm-alldoes not require approve.
Shared Workflow (all /pm-* commands)
- Read config; map-first; redact; confirm before landing generated docs.
- Append audit. Closing:
_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.
- 6d ago First seen · 48 lines · 26 tokens per session scan A 5dfa3e491479
pm-charter is a skill published in the GitHub repository wei63w/pm-manager (99 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 512 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…
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…
create-slack-app
Use when a developer wants to create, scaffold, or bootstrap a new Slack app or agent from scratch with the Slack CLI. Covers prerequisites, sandbox setup, authentication, and creating + running a project from a Bolt (JS or Python) template locally. Trigger on "create a Slack app", "new Bolt app", "start a Slack…
slack-docs
Use when answering a conceptual or how-to question about Slack platform features, or when asked to look up, fetch, or summarize a docs.slack.dev page, including a pasted docs.slack.dev link. Covers finding and reading official Slack docs as clean markdown.