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/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/banibratachatterjee/awesomesalesforceskills/release-notes)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/release-notes"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/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/commands/banibratachatterjee/awesomesalesforceskills/release-notes"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/release-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.00000 | $0.00282 |
| Opus 5 | $0.00000 | $0.00141 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
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.
What it actually says
/release-notes — Release Notes Command
Triggers the release-planner agent.
Usage
/release-notes
Feed in a git diff, component list, or sprint description. Get structured release notes with risk flags and a deployment checklist.
What Happens
- Agent parses input (git diff / component list / PR list / free text)
- Classifies each change by type and risk
- Applies automatic risk flags (sharing changes, trigger modifications, etc.)
- Produces:
- Executive summary (stakeholder-ready, non-technical)
- Changes by type with risk classification
- Breaking change flags
- Deployment checklist (pre/during/post)
- Rollback plan for Critical-risk items
Variants
Specific outputs:
/release-notes — risk assessment only
/release-notes — deployment checklist only
/release-notes — stakeholder summary only
Risk Flag Reference
| Change Type | Default Risk |
|---|---|
| Sharing rule change | 🔴 Critical |
| Permission set change | 🟠 High |
| Trigger modification | 🟠 High |
| New Flow | 🟡 Medium |
| New Apex class | 🟢 Low |
Agent
See agents/release-planner/AGENT.md for full orchestration plan.
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 · 47 lines · 0 tokens per session scan A 834bd16335cb
release-notes is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 282 tokens. 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 commands, from other repositories
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
create-release-note
Generate bug fix release notes from Jira tickets and linked GitHub PRs.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
taupr
The Tau Ceti worker loop — one unit of work per round, first that applies: rebase, fix CI, fix findings, review a stalled PR, else author a new one. Authoring checks the source material first, cleans up, and opens the PR; CI reviews it. We only self-review a PR that CI has left unreviewed for an hour.
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.