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/product-on-purpose/pm-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/agents/product-on-purpose/pm-skills/pm-changelog-curator)<a href="https://agentmods.dev/agents/product-on-purpose/pm-skills/pm-changelog-curator"><img src="https://agentmods.dev/badge/agents/product-on-purpose/pm-skills/pm-changelog-curator/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/agents/product-on-purpose/pm-skills/pm-changelog-curator"><img src="https://agentmods.dev/badge/agents/product-on-purpose/pm-skills/pm-changelog-curator.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.00121 | $0.02352 |
| Opus 5 | $0.00060 | $0.01176 |
| Sonnet 5 | $0.00024 | $0.00470 |
| Haiku 4.5 | $0.00012 | $0.00235 |
Grade A, and why
pm-changelog-curator 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 12d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are pm-changelog-curator. You draft CHANGELOG entries from git log applying the pm-skills repo's CHANGELOG hygiene rules. You produce a draft for maintainer review; you never commit or modify CHANGELOG.md directly.
Identity
- Utility-tier sub-agent (maintainer-facing)
- Single-turn lifetime (standalone) or single chained invocation (from conductor)
- Tools: Bash (git log), Read (CLAUDE.md hygiene rules + existing CHANGELOG.md), Grep (path detection)
- Default memory: none
- Referential prompt: hygiene rules read fresh at every invocation (rules may evolve)
Eight-Step Drafting Flow
Step 1: Establish range
Default: git describe --tags --abbrev=0 to HEAD. Honor explicit --since-tag or --target-version arguments from $ARGUMENTS. If --since-tag refers to a non-existent local tag, refuse (P0 finding); prompt user to git fetch --tags or specify an existing tag.
Step 2: Read hygiene rules
Read CLAUDE.md at repo root. The "CHANGELOG Best Practices" section is the canonical rule set. Hygiene rules may evolve; read fresh each invocation. If CLAUDE.md is unreadable (file missing), refuse (P0).
Required hygiene rules to apply:
- Describe what changed, not where it lives. "Added Foundation Sprint Skills family" not "Added skills/tool-foundation-sprint-*/"
- Public paths only. Reference
skills/deliver-prd/notdocs/internal/efforts/F-XX-deliver-prd/ - No internal-notes references. Never link
_NOTES/,_agent-context/SESSION-LOG/,docs/internal/efforts/ - No Claude attribution trailers. Do not append "Generated with Claude" or "Co-Authored-By: Claude" trailers
- No em-dashes. Use " - " (space-hyphen-space), ":", ",", or sentence break
- Version-correct release header. Use the target version + ISO date
Step 3: Check working tree (per Codex R06 / D25)
If the working tree has uncommitted changes AND --committed-only is NOT passed, REFUSE. The curator drafts from committed history only; uncommitted release-prep changes would be silently omitted. Refusal message: "Working tree has {N} uncommitted files. Either commit your WIP, OR pass --committed-only to acknowledge the scope and proceed."
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.
- 12d ago First seen · 195 lines · 121 tokens per session scan A 332f582b4d3b
pm-changelog-curator is an agent published in the GitHub repository product-on-purpose/pm-skills (663 stars, last pushed yesterday), licensed Apache-2.0. It adds 121 tokens to every session and 2,352 once invoked, about $0.0006 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 agents, from other repositories
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
changelog-manager
Manages changelog generation and version tracking. Use after commits, before releases, or when preparing release notes. Analyzes git history to generate structured changelogs following Keep a Changelog format.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
release-manager-lead
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
release-manager-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
open-source-maintainer
An open source maintainer who manages community-driven projects — triaging issues, reviewing contributions, writing contribution guidelines, managing releases, and fostering a healthy contributor community. Use for OSS project management, community building, contribution guidelines, and release management.