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.
npx skills add mohitagw15856/pm-claude-skills --skill drafted-skillgit 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/skills/mohitagw15856/pm-claude-skills/drafted-skill)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/drafted-skill"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/drafted-skill/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/mohitagw15856/pm-claude-skills/drafted-skill"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/drafted-skill.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.00066 | $0.00598 |
| Opus 5.5 | $0.00026 | $0.00239 |
| Sonnet 5.5 | $0.00013 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
release-notes-from-git-log 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 21d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes From Git Log
Commits are written for the people who made them; release notes are read by the people who did not. This skill turns the log into notes a user can act on: grouped, short, in plain language, with internal noise removed.
What This Skill Produces
- A headline line for the release
- Changes grouped under Features, Fixes, and Changes, one line each, user-facing
- A migration note when anything needs action
Required Inputs
Ask for these if not provided:
- The git log (or the commit list) since the last tag
- The version or tag name
- The audience: end users, developers, or both
Framework: Group, Translate, Cut
- Group by kind from the commit prefix or message: feat, fix, chore.
- Translate each line from what changed to what the reader gains.
- Cut chores, refactors and merges unless they change behaviour.
Output Format
v:
Features
- ... Fixes
- ... Changes
- ... Migration: <none, or the one step>
Worked Examples
Example 1: a small web app release
Input (abridged): 12 commits, three prefixed feat, six fix, three chore. Output (abridged): a headline, three feature lines, six fix lines, no chores, migration: none.
Example 2: a library with a breaking change
Input (abridged): a commit renaming a public function. Output (abridged): the rename under Changes with the old and new name, and a one-line migration step.
Example 3: a hotfix
Input (abridged): one fix commit. Output (abridged): a single-line note with the headline "hotfix" and the fix.
Quality Checks
- Every line says what the reader gains, not what the code did
- Chores and merges are gone unless they change behaviour
- Grouped, one line per change, short
- A migration note exists whenever something needs action
Anti-Patterns
- Pasting commit messages. They are not notes.
- Listing every commit. Cut the noise.
- Internal tone. Ticket numbers and branch names do not belong.
Example Trigger Phrases
- "Release notes from this git log."
- "Write the changelog entry from these commits."
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 21d ago First seen · 62 lines · 66 tokens per session scan A 025182b0ebc9
release-notes-from-git-log is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 598 once invoked, about $0.0003 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…