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 HoangNguyen0403/agent-skills-standard --skill publish-notesgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/publish-notes)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/publish-notes"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/publish-notes/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/hoangnguyen0403/agent-skills-standard/publish-notes"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/publish-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.00778 |
| Opus 5.5 | $0.00008 | $0.00311 |
| Sonnet 5.5 | $0.00004 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
publish-notes 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 11d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Notes Skill
[!IMPORTANT] Draft user-facing release notes, store changelogs, and internal publish summaries.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
Publish Notes Workflow
Goal: Convert verified changes into accurate user-facing and internal release notes.
Steps
- Gather inputs:
- Merged commits or diff, PR description, verification report, UAT signoff, and deployment report.
- Product or store constraints.
- When initiative uses product evidence (
docs/product/<slug>/evidence.json), carry measurement owner, registered MET baseline OR exact scoped exception DEC, query, instrumentation, cohort, window, guardrails, and review trigger; never fabricate agent-created baselines, approvals, or causal ROI. - Load
common-operator-profile; carry inheritedoperator_profilefrom Handoff Payload without re-inferring it.
- Triage impact:
- User-facing change
- Bug fix
- Security or privacy note
- Operational change
- No-user-impact internal change
- Draft notes:
- Use plain language and business outcomes for every tier;
operator_profile=businessgets Public Notes as the primary artifact, Internal Notes as an appendix. - Keep sensitive security details high-level.
- Respect platform character limits.
- Use plain language and business outcomes for every tier;
- Verify and persist:
- Cross-check notes against shipped scope; remove unshipped claims.
- Separate delivery proof from observed business success: shipping verified software does not prove positive customer value or ROI. Feature
feature_status=releasedis retained even when product value is pending or inconclusive. - Write run record to
artifacts/runs/[slug]/[compactISO]-publish-notes.jsonwhen file writes allowed. - Route process lessons to
retro-learn.
Runtime Contract
- Use after
deploy-releaseoruat-signoffto draft user-facing and internal release communication. - Required inputs: shipped diff/commits plus verification or deployment report to cross-check against.
- Return BLOCKED only when no verified shipped scope exists to draft notes from. Feature released status is retained when product value is pending or inconclusive.
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.
- 11d ago Changed · -3 lines 0acefa6945b5
- 27d ago Changed · +1 lines db00065068bf
- 1mo ago Changed · -1 lines 8ea1a652d5ed
- 1mo ago First seen · 85 lines · 20 tokens per session scan A c5d98d251b87
publish-notes is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 778 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-03.
Other skills, from other repositories
oma-scm
Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
oma-dev-workflow
Configure development tasks, git hooks, CI/CD, or release automation. Use when creating or fixing a repository development workflow.
github-release
Prepare and publish GitHub releases. Sanitizes code for public release (secrets scan, personal artifacts, LICENSE/README validation), creates version tags, and publishes via gh CLI. Trigger with 'release', 'publish', 'open source', 'prepare for release', 'create release', or 'github release'.
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
ship
Comprehensive pre-deployment verification to ensure release readiness.