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/hiepdnh/agentic-development-lifecycle/pm-releasenpx skills add hiepdnh/Agentic-Development-Lifecycle --skill pm-releasegit clone --depth 1 https://github.com/hiepdnh/Agentic-Development-LifecycleWrote 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/hiepdnh/agentic-development-lifecycle/pm-release)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/pm-release"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/pm-release.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.00082 | $0.01200 |
| Opus 5 | $0.00041 | $0.00600 |
| Sonnet 5 | $0.00016 | $0.00240 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
pm-release 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /pm-release
Role: PM / Bridge Engineer
Mục đích: Tạo Release Notes từ merged PRs + closed issues — đủ để gửi khách JP như một deliverable chính thức.
Hướng dẫn thực hiện
Bước 1 — Gate: Xác định phạm vi release
Dùng AskUserQuestion tool:
- Version/Sprint: Release v[X.Y.Z] / Sprint [N] / Hotfix [date]
- Audience: Team internal / Khách hàng JP / Management / Public
- Format output: HTML (recommend cho JP delivery) / Markdown (Slack/Notion/commit) / Cả hai
Chờ confirm.
Bước 2 — Thu thập dữ liệu
Spawn subagent để đọc:
Agent(
description: "Collect release data from git and task docs",
prompt: "Read the following and return structured JSON:
1. git log --oneline --merges [base-tag]..HEAD — list of merged PRs
2. git tag --sort=-version:refname | head -5 — recent tags
3. List all docs/tasks/*/requirements.md for tasks completed this sprint
4. List docs/tasks/*/verification.md for sign-off status
Return JSON: { mergedPRs: [...], closedTasks: [...], openTasks: [...], tagHistory: [...] }
Read only, no changes.",
model: "haiku"
)
Bước 3 — Phân loại thay đổi
Phân loại tự động từ PR titles + task descriptions:
| Category | Tiếng Việt | 日本語 |
|---|---|---|
| New Feature | Tính năng mới | 新機能 |
| Bug Fix | Sửa lỗi | バグ修正 |
| Improvement | Cải tiến | 改善 |
| Performance | Hiệu năng | パフォーマンス改善 |
| Security | Bảo mật | セキュリティ |
| Breaking Change | Thay đổi không tương thích | 互換性のない変更 |
| Maintenance | Bảo trì nội bộ | メンテナンス |
Bước 4 — Tạo Release Notes
Format HTML (option A — cho JP delivery)
Sinh docs/reports/release-[version]-[date].html từ template templates/html-artifact.html:
- Header: Release [version] · [Date JST] · badge "リリース済み"
- Section 新機能 / New Features: cards với icon ✨, mô tả JP + VN
- Section バグ修正 / Bug Fixes: cards với icon 🐛
- Section 改善 / Improvements: cards với icon ⚡
- Section ⚠️ 互換性のない変更 / Breaking Changes: nếu có, highlight đỏ
- Footer: link đến repo, PR list, Contact BE
What ships with it
2 files 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.
- 6d ago First seen · 114 lines · 82 tokens per session scan A 2a86f105718e
pm-release is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 9d ago), licensed MIT. It adds 82 tokens to every session and 1,200 once invoked, about $0.0004 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-31.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…