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/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/commands/hoangnguyen0403/agent-skills-standard/publish-notes)<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/publish-notes"><img src="https://agentmods.dev/badge/commands/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/commands/hoangnguyen0403/agent-skills-standard/publish-notes"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/publish-notes.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.00016 | $0.00465 |
| Opus 5 | $0.00008 | $0.00233 |
| Sonnet 5 | $0.00003 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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 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.
What it actually says
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
- Deployment report
- Product or store constraints
- Load
common-operator-profile; carry the inheritedoperator_profilefrom the 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:
- Cross-check notes against shipped scope.
- Remove unshipped claims.
- 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 a verification or deployment report to cross-check against.
- Return BLOCKED only when no verified shipped scope exists to draft notes from.
Handoff Payload
slug,operator_profile, public notes, internal notes, security/privacy notes, verification source, next workflow.
Blocking Questions
- Ask max 3 at a time with a recommended default and 2-3 options.
Output Template
# Release Notes: [Version]
## Public Notes
## Internal Notes
## Security Or Privacy Notes
## Verification Source
## Outcome Report
feature_status: implemented
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: retro-learn
## Next Workflow
retro-learn
## Cost Report
Call `get_session_cost(workflow="publish-notes")` before final handoff.
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 · 67 lines · 16 tokens per session scan A bc52a8e203e2
publish-notes is a command published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 465 once invoked, about $0.0001 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-09-06.
Other commands, from other repositories
ralph
Ralph - persistent self-referential execution loop wrapping ultrawork with a spawned independent judge.
tools
Manage MCP tools with natural language commands to list, enable, and disable tools and tool groups.
incident
An incident-response assistant for guiding work when a software service has a serious failure or disruption.
scan
A security scanning assistant command with guidance on its workflow, usage, and how an AI agent should behave during a scan.
page
Create Next.js page following mirror pattern.
checklist
Generate a custom checklist for the current feature based on user requirements.