agentmods.dev

changelog

changelog is a skill for Claude Code from KingGyuSuh/gemini-search-cc. It costs 15 tokens per session (452 once invoked), scanned A, original, Apache-2.0.

A lookup tool for the latest release notes and breaking changes for a software package or technology.

In plain words
What is it for?
Use it to find a package’s newest version, release date, and upgrade-related breaking changes. It can also check the project’s dependency files for the installed version.
Why use it?
It helps you check what changed before upgrading, so you can spot changes that might require code updates.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the gemini plugin — 9 skills, 3 hooks shipped together

not rated 3repo 2mo ago A scan 15 tokens original Apache-2.0

Good fit Use it to find a package’s newest version, release date, and upgrade-related breaking changes. It can also check the project’s dependency files for the installed version.

Compare 6 skills from other repositories ↓
View source ↗ KingGyuSuh/gemini-search-cc
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add KingGyuSuh/gemini-search-cc
Claude Code
/plugin install gemini

Made for: Claude Code.

Or install gemini, the plugin that ships this one along with the rest of its 9 skills, 3 hooks.

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 changelog

README.md
[![agentmods](https://agentmods.dev/badge/skills/kinggyusuh/gemini-search-cc/changelog/github.svg)](https://agentmods.dev/skills/kinggyusuh/gemini-search-cc/changelog)
Your own site
<a href="https://agentmods.dev/skills/kinggyusuh/gemini-search-cc/changelog"><img src="https://agentmods.dev/badge/skills/kinggyusuh/gemini-search-cc/changelog/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 changelog

Your own site · 80×15
<a href="https://agentmods.dev/skills/kinggyusuh/gemini-search-cc/changelog"><img src="https://agentmods.dev/badge/skills/kinggyusuh/gemini-search-cc/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 452 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.00015 $0.00452
Opus 5 $0.00008 $0.00226
Sonnet 5 $0.00003 $0.00090
Haiku 4.5 $0.00002 $0.00045

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

Security

Grade A, and why

changelog 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 11d 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.

plugins/gemini/skills/changelog/SKILL.md · 48 lines

What it actually says

Fetch the latest release notes, changelog, and breaking changes for a specific package or technology using the Antigravity CLI's grounded Google Search.

Use this before upgrading dependencies, adopting new versions, or investigating what changed between releases.

Raw slash-command arguments: $ARGUMENTS

Steps

  1. If $ARGUMENTS is empty, use AskUserQuestion to ask which package to check.

  2. Gather local context (optional but recommended):

    • Use Glob and Read to check dependency manifests (package.json, requirements.txt, Cargo.toml, go.mod, etc.) for the current installed version of the package.
    • If found, include the current version in the query for more targeted results.

  3. Run the companion script:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" changelog "$ARGUMENTS"

  4. If the command fails:

    • Run node "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-companion.mjs" setup to diagnose.
    • Show the diagnosis to the user.

  5. Return the output verbatim.

  6. After the results, provide a Changelog Summary:

    • Latest Version: version number and release date
    • Breaking Changes: list any breaking changes (if upgrading)
    • Migration Required: Yes / No — with brief description if yes
    • Recommendation: Safe to upgrade / Review changes first / Wait for patch

Constraints

  • Do not paraphrase the search output.
  • Be precise about version numbers — say "v4.2.1" not "a recent version."
  • If the search returns changelogs for a different version than requested, note the discrepancy.
  • Do not auto-update any dependencies. Only advise.
  • Prefer official sources (GitHub releases, npm, PyPI) over third-party summaries.
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. 11d ago First seen · 48 lines · 15 tokens per session scan A dbcf98c72271

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository KingGyuSuh/gemini-search-cc (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 452 once invoked, about $0.0001 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.

Claude CodeGit and workflowReleasesResearchclaude-code-plugindeep-researchfact-checkinggeminigoogle-search
Related

Other skills, from other repositories

release

Trigger the CI release pipeline for gemini-plugin-cc. Maintainer-only.

abiswas97/gemini-plugin-cc · 18 tokens

release

Cut a release of the video-intel plugin. Use when tagging a version, bumping .claude-plugin/plugin.json, pushing tags, publishing a GitHub Release, or answering how this plugin is distributed and installed by end users.

dzivkovi/video-intel · 49 tokens

release

Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.

BlockRunAI/ClawRouter · 44 tokens

close-task-commit-push-pr

Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.

devoxx/DevoxxGenieIDEAPlugin · 64 tokens

release

CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.

oliver-kriska/claude-elixir-phoenix · 60 tokens

release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…

hyhmrright/brooks-lint · 135 tokens