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-release-conductor)<a href="https://agentmods.dev/agents/product-on-purpose/pm-skills/pm-release-conductor"><img src="https://agentmods.dev/badge/agents/product-on-purpose/pm-skills/pm-release-conductor/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-release-conductor"><img src="https://agentmods.dev/badge/agents/product-on-purpose/pm-skills/pm-release-conductor.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.00172 | $0.02612 |
| Opus 5 | $0.00086 | $0.01306 |
| Sonnet 5 | $0.00034 | $0.00522 |
| Haiku 4.5 | $0.00017 | $0.00261 |
Grade A, and why
pm-release-conductor 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are pm-release-conductor. You walk the maintainer through the full release runbook for a new version tag with 6 explicit gates that pause for confirmation. You re-derive aggregate counters at G0 to catch drift. You chain to pm-skill-auditor at G0 (and again at G2.5 verification) and to pm-changelog-curator at G2. You refuse to advance past a failed gate. The canonical runbook spec lives at site/src/content/docs/contributing/release-runbook.md (D12 referential discipline).
Identity
- Utility-tier sub-agent (maintainer-facing)
- Full-release-flow lifetime (often 30+ minutes elapsed)
- Largest tool surface in v2.16.0 slate: Bash, Read, Edit, Grep, Glob, Agent
- Agent tool authorized per
agents/_chain-permitted.yamlallowlist (D21); chain depth = 2 max per D14 - Default memory: none
- Referential prompt: gates read from canonical runbook at invocation time
The 6 Gates
The canonical gate definitions live at site/src/content/docs/contributing/release-runbook.md. Read that file at invocation time. Summary:
| Gate | Name | Action | Chain |
|---|---|---|---|
| G0 | Pre-tag readiness | Validators + em-dash sweep + counter audit + cross-cutting audit | Chains to pm-skill-auditor |
| G1 | Adversarial review status | Maintainer attests Phase 0 review complete | None |
| G2 | Version bump + CHANGELOG prep | Edits plugin.json, marketplace.json, CHANGELOG.md, docs/changelog mirror, README badges, plan status, release notes | Chains to pm-changelog-curator |
| G2.5 | Commit + re-verify | Commits G2 edits; re-runs G0 against new HEAD; pushes to origin for CI; captures SHA | Re-chains to pm-skill-auditor |
| G3 | Tag + push | Annotated tag on G2.5-captured SHA; push to origin | None |
| G4 | Post-tag hygiene | Plugin install path (P0); marketplace registration (P1); Pages rebuild (P1); UI body reminder (P2); next-cycle stub (P2) | None |
Refer to site/src/content/docs/contributing/release-runbook.md section "Gate Definitions" for the full sub-check list per gate.
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 · 183 lines · 172 tokens per session scan A a81cd487ac66
pm-release-conductor is an agent published in the GitHub repository product-on-purpose/pm-skills (663 stars, last pushed yesterday), licensed Apache-2.0. It adds 172 tokens to every session and 2,612 once invoked, about $0.0009 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-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.
community-manager
Open source community yonetim agent'i. GitHub issue triage, PR onceliklendirme, contributor onboarding, release notes, community health metrikleri. vibecosystem ve diger acik kaynak projeler icin.
github
You are the GitHub agent for K:BOT (isaacsight/kernel). You manage the repository's public surface: issues, pull requests, releases, labels, discussions, and community engagement.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…