agentmods.dev

sf-release-notes

sf-release-notes is a skill for Claude Code from divingsbysangam/salesforce-compound-engineering-plugin. It costs 56 tokens per session (507 once invoked), scanned A, original, MIT.

A release-note generator for Salesforce packages and plugins, where a package is a distributable bundle of Salesforce functionality. It summarizes changes from pull requests, commits, and changelog entries.

In plain words
What is it for?
Use it when releasing managed or unlocked Salesforce packages or plugins, with sections for additions, changes, fixes, and breaking changes.
Why use it?
It saves time when turning development history into user-facing release information and highlights breaking changes that may require updates.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool; mentions Claude Code.

Part of the sf-compound-engineering plugin — 68 skills, 2 agents, 1 hook, 2 MCP servers shipped together

not rated 10 2d ago A scan 56 tokens original MIT
View the source file divingsbysangam/salesforce-compound-engineering-plugin
Install

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.

agentmods
npx agentmods add skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-release-notes
Any agent
npx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-release-notes
Clone the repo
git clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-plugin

Made for: Claude Code.

Or install sf-compound-engineering, the plugin that ships this one along with the rest of its 68 skills, 2 agents, 1 hook, 2 MCP servers.

Wrote 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.

agentmods badge for sf-release-notes

README.md
[![agentmods](https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-release-notes.svg)](https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-release-notes)
Your own site
<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-release-notes"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-release-notes.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 507 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.00507
Opus 5 $0.00028 $0.00253
Sonnet 5 $0.00011 $0.00101
Haiku 4.5 $0.00006 $0.00051

Measured 6d ago against content hash 505b3318e367, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

sf-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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/sf-release-notes/SKILL.md · 38 lines

How it starts

The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.

sf-release-notes

Produce structured release notes (Added / Changed / Fixed / BREAKING) from git history.

<feature_description> #$ARGUMENTS </feature_description>

Salesforce Angle

  • Salesforce package version names follow <major>.<minor>.<patch>-<build> for managed packages.
  • Surface BREAKING for: removed fields, removed picklist values, changed Apex method signatures, changed @RestResource URL bindings.

Interaction Method

When asking the user a question, use the platform's blocking question tool (AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini). Fall back to numbered options in chat when no blocking tool is available. Ask one question at a time. Prefer concise single-select choices when natural options exist.

Procedure

This skill follows the standard sf-compound-engineering execution discipline:

  1. Understand the input — read the <feature_description> block above and any referenced files, plans, or issues.
  2. Plan a small set of phases — break the work into 2-5 ordered steps that an implementer (or another skill) can verify.
  3. Apply the Salesforce Angle notes above — these encode the platform-specific considerations (governor limits, sharing context, deploy ordering, FLS, metadata semantics) that distinguish this skill from generic counterparts.
  4. Use Salesforce-aware contexts and commands — file paths under force-app/main/default/..., test commands like sf apex run test, deploy commands like sf project deploy validate and sf project deploy start, query the org with sf data query when state inspection is needed.
  5. Surface decisions back to the user — when a step requires a choice that materially affects scope or risk, ask using the platform's blocking question tool rather than guessing.
  • Salesforce knowledge: docs/solutions/ (search via the sf-learnings-researcher agent).
  • Plugin conventions: see CLAUDE.md for frontmatter, naming, and protected-artifact rules.

Read the full file on GitHub · 38 lines

Changes

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.

  1. 6d ago First seen · 38 lines · 56 tokens per session scan A 505b3318e367

Subscribe to this mod's changes

sf-release-notes is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 507 once invoked, about $0.0003 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.

Git and workflowReleases
Related

Other skills, from other repositories

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

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.

paperclipai/paperclip · 42 tokens

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.

openai/symphony · 42 tokens

changelog

Create changelog files for important commits in a PR.

pipecat-ai/pipecat · 13 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

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…

Azure/azure-sdk-for-net · 91 tokens