PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
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.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skillsWrote 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/commands/mohitagw15856/pm-claude-skills/promote)<a href="https://agentmods.dev/commands/mohitagw15856/pm-claude-skills/promote"><img src="https://agentmods.dev/badge/commands/mohitagw15856/pm-claude-skills/promote/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/commands/mohitagw15856/pm-claude-skills/promote"><img src="https://agentmods.dev/badge/commands/mohitagw15856/pm-claude-skills/promote.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.00030 | $0.00461 |
| Opus 5.5 | $0.00012 | $0.00184 |
| Sonnet 5.5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
promote 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 23d 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
Run the promote loop for: $ARGUMENTS
This is a chain of four skills with one decision in the middle and one confirmation at the end. Carry every stage's output forward as context. Open with a one-line plan, then ask once for anything essential that is missing (where the transcripts are; which bundle a promoted skill should join).
Run each stage under a clear ## Stage N — <name> heading:
- Scan — apply the
promoter-scanskill to the transcripts: runscripts/promoter_scan.pyon the path, then present the ranked report of recurring patterns with redacted examples and a promotability score. Stop and ask the user which pattern to promote (offer the top three with the one-line reason each). Do not continue until they choose. - Draft — apply the
promoter-draftskill to the chosen pattern: writeskills/<name>/SKILL.mdin the library's format with three worked examples generalised from the user's prompts, the collision check against existing skills, and the bundle stanza. Show the description first, then the file. - Test — apply the
promoter-testskill: writeevals.jsonwith positives, near-miss negatives and goldens, runscripts/promoter_test.py, report precision and recall, rewrite the description and re-run if precision is below 0.8. Add the case toevals/cases.json. - Publish — apply the
promoter-publishskill: produce the full release package (wiring, generators, count, gates, version, CHANGELOG, commands). Ask "Confirm to push?" once, and only run the git and release commands after a yes.
Close with the release note (three lines) and the one thing the user should watch after the release: the CI run and the playground picking up the new skill.
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.
- 23d ago First seen · 18 lines · 30 tokens per session scan A f3910064d929
promote is a command published in the GitHub repository mohitagw15856/pm-claude-skills (1,463 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 461 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-09-23.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.