Borrowing it
Nothing to install: this file belongs to opensupplyhub/open-supply-hub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opensupplyhub/open-supply-hub/main/.agent/skills/confluence-release-notes/SKILL.mdgit clone --depth 1 https://github.com/opensupplyhub/open-supply-hubWrote 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/opensupplyhub/open-supply-hub/confluence-release-notes)<a href="https://agentmods.dev/skills/opensupplyhub/open-supply-hub/confluence-release-notes"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/confluence-release-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/opensupplyhub/open-supply-hub/confluence-release-notes"><img src="https://agentmods.dev/badge/skills/opensupplyhub/open-supply-hub/confluence-release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 99 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Agent Snooping · line 174 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00094 | $0.02184 |
| Opus 5 | $0.00047 | $0.01092 |
| Sonnet 5 | $0.00019 | $0.00437 |
| Haiku 4.5 | $0.00009 | $0.00218 |
Grade A, and why
confluence-release-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 9d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confluence Release Notes & Slack Post
| # | Artifact | Destination |
|---|---|---|
| 1 | Confluence page (metadata + description + Programs warning + issue table) | Draft in SD space via createConfluencePage |
| 2 | Slack post (org-wide summary + Confluence link) | Chat only — user posts manually |
Out of scope: Info-site publishing decisions (Programs Team). Do not recommend what Programs should publish externally beyond filling the issue table's external column with suggested values.
Rules
GitHub doc/release/RELEASE-NOTES.md is the source of truth for ticket membership and release date. Build an allowlist from the target ## Release X.Y.Z section only (OSDEV-\d+, deduplicated). Every narrative bullet and issue-table row must match the allowlist exactly — one row per ticket, no extras, no missing.
Jira supplies summaries, descriptions, assignees, and sprints for allowlisted tickets only. Never add tickets from Jira Fix Version, prior Confluence pages, or memory.
Never invent information. If uncertain about grouping, sprint, or ticket membership, ask the user — do not guess.
Prior Confluence pages in the Release Notes folder supply page format and Description tone only. Load the latest via getConfluencePage; fallback: 2.25.0.
Facts-only: never invent information. [Follow-up] items in GitHub count if under the target release section. When Jira Fix Version lists tickets not in GitHub, omit them and note the discrepancy after filing.
Workflow
- Confirm release version (if not provided).
- Read GitHub —
Readdoc/release/RELEASE-NOTES.md; extract the## Release X.Y.Zsection, release date, and ticket allowlist. - Load format reference —
searchConfluenceUsingCql(ancestor = 649494530, order bylastmodified DESC) →getConfluencePage(contentFormat: html). If a page for this release already exists, update it instead of creating a duplicate. - Fetch Jira —
searchJiraIssuesUsingJqlfor allowlisted keys only:cloudId: opensupplyhub.atlassian.netfields: summary, description, assignee, customfield_10020, fixVersions- Paginate with
nextPageTokenif >50 tickets - Release link: Jira Fix Version URL from
fixVersions— do not invent version IDs
- Infer Sprint — sprint with the most tickets (e.g.
Sprint 84). Add an italic clarifying note only when tickets span multiple sprints. - Contributors — unique Jira assignees, space-separated
@Name. - Draft narrative — themed, business-oriented (see Description).
- Checkpoint in chat (required; never skip) — metadata table with full Description in the Description row, Programs warning, issue table, then Slack post draft. Use
(Confluence link — added after draft page is created)in Slack.
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.
- 9d ago First seen · 175 lines · 94 tokens per session scan A 4983e55e815d
confluence-release-notes is a skill published in the GitHub repository opensupplyhub/open-supply-hub (20 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 2,184 once invoked, about $0.0005 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 skills, from other repositories
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.