github-release-briefing-skill

github-release-briefing-skill is a skill for Claude Code from FrancyJGLisboa/agent-skill-creator. It costs 45 tokens per session (460 once invoked), scanned A, original, MIT.

A briefing generator for the newest published release of a public GitHub repository. GitHub is a service where developers host source code and publish project releases.

In plain words
What is it for?
Use it to track a dependency's latest release, including its tag, title, date, and release page URL. It does not publish releases, change repositories, or download release files.
Why use it?
It saves engineering teams from manually checking release details and provides the source link used for the briefing. It also clearly reports when no published release is available.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the agent-skill-creator plugin — 5 skills, 1 plugin shipped together

Good fit Use it to track a dependency's latest release, including its tag, title…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/francyjglisboa/agent-skill-creator/github-release-briefing-skill
About the project

Agent Skills Platform turns documented work and supporting evidence into tested, installable skills for coding agents. Teams use it to review, publish, maintain, and safely reuse agent workflows, with the catalogue entries serving as skills and plugins built for that ecosystem.

FrancyJGLisboa/agent-skill-creator · 2,378 stars · on GitHub · francyjglisboa.github.io

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.

Any agent
npx skills add FrancyJGLisboa/agent-skill-creator --skill github-release-briefing-skill
Clone the repo
git clone --depth 1 https://github.com/FrancyJGLisboa/agent-skill-creator

Made for: Claude Code.

Or install agent-skill-creator, the plugin that ships this one along with the rest of its 5 skills, 1 plugin.

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 github-release-briefing-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/francyjglisboa/agent-skill-creator/github-release-briefing-skill.svg)](https://agentmods.dev/skills/francyjglisboa/agent-skill-creator/github-release-briefing-skill)
Your own site
<a href="https://agentmods.dev/skills/francyjglisboa/agent-skill-creator/github-release-briefing-skill"><img src="https://agentmods.dev/badge/skills/francyjglisboa/agent-skill-creator/github-release-briefing-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 460 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.00045 $0.00460
Opus 5 $0.00023 $0.00230
Sonnet 5 $0.00009 $0.00092
Haiku 4.5 $0.00005 $0.00046

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

Security

Grade A, and why

github-release-briefing-skill 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 7d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/run_evals.py, scripts/run_pipeline.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

references/examples/github-release-briefing-skill/SKILL.md · 57 lines

What it actually says

/github-release-briefing-skill

Create a current briefing for the latest published release of one public GitHub repository. Run scripts/run_pipeline.py with an OWNER/REPOSITORY input. The command uses GitHub's public REST endpoint, writes a Markdown briefing, and does not authenticate, publish, modify a repository, or download release assets.

python3 scripts/run_pipeline.py --repository openai/openai-python --output release.md

Required behavior

  1. Reject malformed repository identifiers before any request.
  2. Retrieve only the latest published release and identify its tag, title, date, and URL.
  3. State clearly when a repository has no published release or is unavailable.
  4. Include the GitHub API source URL so a human can inspect the result.

Gotchas

  • A GitHub "latest" release excludes drafts and prereleases according to the API's rules.
  • This is dependency-awareness evidence, not a change-approval recommendation.
  • Public API availability and release content can change after retrieval.

References

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. 7d ago First seen · 57 lines · 45 tokens per session scan A f48df6441f0b

Subscribe to this mod's changes

github-release-briefing-skill is a skill published in the GitHub repository FrancyJGLisboa/agent-skill-creator (2,378 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 460 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

ijfw-ship

Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…

FerroxLabs/ijfw · 139 tokens

ijfw-preflight

Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.

FerroxLabs/ijfw · 47 tokens

github-pr-merge

Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.

myths-labs/muse · 72 tokens

git-authoring

Authors and executes git work end to end — Conventional Commits messages, pull-request content, release notes, and pull-request review, plus the repository operations an engineer runs daily: branching, rebasing, squashing, cherry-picking, reverting, merge-conflict resolution, stashes, tags, remotes, and recovery…

n-shadloo/git-authoring · 220 tokens

release-verification

A release-verification checklist for software versions and packages. It covers changelogs, tests, packaging, installation smoke checks, version-control actions, publishing, and checks after release.

devcodex-labs/devcodex · 39 tokens

audit-release

A pre-release review assistant that checks whether a software package or plugin is ready to publish.

devcodex-labs/devcodex · 104 tokens