phantom-connect-sdk: Skill for Claude Code

.claude/skills/generate-release-notes/SKILL.md

generate-release-notes is a skill for Claude Code from phantom/phantom-connect-sdk. It costs 0 tokens per session (1,123 once invoked), scanned A, original, MIT.

A guide for writing release notes from the changes between a Git tag and the current code. A Git tag is a named point in a project’s history, often marking a release.

In plain words
What is it for?
Use it to compare a release tag with the current codebase and produce notes for one package or all packages.
Why use it?
It summarises code changes at a high level and can limit the summary to one package or cover the whole repository.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is phantom/phantom-connect-sdk's own configuration. It tells Claude Code how to work on phantom-connect-sdk itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything phantom-connect-sdk configures →

Reuse

Borrowing it

Nothing to install: this file belongs to phantom/phantom-connect-sdk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/phantom/phantom-connect-sdk/main/.claude/skills/generate-release-notes/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/phantom/phantom-connect-sdk

Made for: Claude Code.

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 generate-release-notes

README.md
[![agentmods](https://agentmods.dev/badge/skills/phantom/phantom-connect-sdk/generate-release-notes/github.svg)](https://agentmods.dev/skills/phantom/phantom-connect-sdk/generate-release-notes)
Your own site
<a href="https://agentmods.dev/skills/phantom/phantom-connect-sdk/generate-release-notes"><img src="https://agentmods.dev/badge/skills/phantom/phantom-connect-sdk/generate-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.

agentmods 80×15 button for generate-release-notes

Your own site · 80×15
<a href="https://agentmods.dev/skills/phantom/phantom-connect-sdk/generate-release-notes"><img src="https://agentmods.dev/badge/skills/phantom/phantom-connect-sdk/generate-release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,123 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00000 $0.01123
Opus 5.5 $0.00000 $0.00449
Sonnet 5.5 $0.00000 $0.00225
Haiku 4.5 $0.00000 $0.00112

Measured 1mo ago against content hash f23bd11307e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

generate-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 1mo 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.

.claude/skills/generate-release-notes/SKILL.md · 140 lines

How it starts

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

Skill: generate-release-notes

Generate a high-level release note summarising what changed between a git tag and the current codebase.

Arguments: <tag> [package] — a git tag to diff against (e.g. v1.2.0, @phantom/[email protected]), and an optional package name to scope the diff (e.g. @phantom/react-sdk). If no package is provided, all packages are included.

Note: Release tags live on https://github.com/phantom/phantom-connect-sdk. The diff is always performed against the current checkout.


Phase 0 — Determine scope

Parse the arguments:

  • {tag} — the first argument (required)
  • {package} — the second argument (optional)

If {package} is provided, scope all git diff/log commands to packages/{package-dirname}/ where {package-dirname} is derived from the package name (e.g. @phantom/react-sdk → react-sdk). Use the package name in the output filename.

If {package} is not provided, run commands without a path filter to capture all packages, and use all in the output filename.


Phase 1 — Resolve the tag commit from the public repo

This checkout may not have release tags. Fetch the commit SHA that the tag points to from the release repository:

# Get the commit SHA the tag resolves to in the release repository
git ls-remote https://github.com/phantom/phantom-connect-sdk.git "refs/tags/{tag}" "refs/tags/{tag}^{}"

Take the last SHA returned (the dereferenced ^{} entry if present, otherwise the only entry). Call this {public-sha}.

Then verify this commit exists in the current checkout:

git -C <repo-root> cat-file -t {public-sha}

If the commit is not found, the local checkout and release repository may have diverged in history. Stop and report this to the user.


Phase 2 — Gather raw data

Run the following from the repo root using {public-sha} as the base:

# List commits between the tag SHA and HEAD (scoped to package path if provided)
git log {public-sha}...HEAD --oneline --no-merges [-- packages/{package-dirname}/]

# Full diff summary
git diff {public-sha}...HEAD --stat [-- packages/{package-dirname}/]

# Detailed diff
git diff {public-sha}...HEAD [-- packages/{package-dirname}/]

Read the full file on GitHub · 140 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. 1mo ago Changed f23bd11307e8
  2. 2mo ago First seen · 140 lines · 0 tokens per session scan A 9fb2dd6ff99f

Subscribe to this mod's changes

generate-release-notes is a skill published in the GitHub repository phantom/phantom-connect-sdk (165 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,123 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-08-30.