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.
npx agentmods add skills/google-gemini/gemini-cli/docs-changelognpx skills add google-gemini/gemini-cli --skill docs-changeloggit clone --depth 1 https://github.com/google-gemini/gemini-cliWhat 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 | $0.00025 | $0.01913 |
| Opus 5 | $0.00013 | $0.00957 |
| Sonnet 5 | $0.00005 | $0.00383 |
| Haiku 4.5 | $0.00003 | $0.00191 |
Grade A, and why
docs-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 3d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- docs-changelog — 100% identical, 0 lines differ
- docs-changelog — 92% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Procedure: Updating Changelog for New Releases
Objective
To standardize the process of updating changelog files (latest.md,
preview.md, index.md) based on automated release information.
Inputs
- version: The release version string (e.g.,
v0.28.0,v0.29.0-preview.2). - TIME: The release timestamp (e.g.,
2026-02-12T20:33:15Z). - BODY: The raw markdown release notes, containing a "What's Changed" section and a "Full Changelog" link.
Guidelines for latest.md and preview.md Highlights
- Aim for 3-5 key highlight points.
- Each highlight point must start with a bold-typed title that summarizes the
change (e.g.,
**New Feature:** A brief description...). - Prioritize summarizing new features over other changes like bug fixes or chores.
- Avoid mentioning features that are "experimental" or "in preview" in Stable Releases.
- DO NOT include PR numbers, links, or author names in these highlights.
- Refer to
.gemini/skills/docs-changelog/references/highlights_examples.mdfor the correct style and tone.
Initial Processing
- Analyze Version: Determine the release path based on the
versionstring.- If
versioncontains "nightly", STOP. No changes are made. - If
versionends in.0, follow the Path A: New Minor Version procedure. - If
versiondoes not end in.0, follow the Path B: Patch Version procedure.
- If
- Process Time: Convert the
TIMEinput into two formats for later use:yyyy-mm-ddandMonth dd, yyyy. - Process Body:
- Save the incoming
BODYcontent to a temporary file for processing. - In the "What's Changed" section of the temporary file, reformat all pull
request URLs to be markdown links with the PR number as the text (e.g.,
[#12345](URL)). - If a "New Contributors" section exists, delete it.
- Preserve the "Full Changelog" link. The processed content of this temporary file will be used in subsequent steps.
- Save the incoming
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 169 lines · 25 tokens per session scan A accc09bf6ded
docs-changelog is a skill published in the GitHub repository google-gemini/gemini-cli (106,761 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 1,913 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-30.
Other skills, from other repositories
bump-version
Use when bumping the AionUi version: query AionCore release, verify artifacts, update package.json, generate CHANGELOG, branch, commit, push, create PR, auto-merge, tag release.
gemini-omni-flash-api
Use this skill for generative video editing, text-to-video, image-referenced video generation, first-frame-to-video, first-and-last-frame transitions, and video extensions using Gemini Omni 1.1 Flash (gemini-omni-1.1-flash) via the official google-genai SDK. Includes workflows for pre-processing/optimizing…
gemini-api-dev
Use this skill when writing code that calls the Gemini API for text generation, multi-turn chat, multimodal understanding, image generation, video generation, streaming responses, background research tasks, function calling, structured output, or migrating from the old generateContent API. Covers SDK usage and best…
changelog-writer
Write changelogs for Bifrost releases. Reads git history, bumps module versions following the core→framework→plugins→transport hierarchy, writes transports/changelog.md (enterprise-style) and per-module changelog.md files, and updates version files. Invoked with /changelog-writer or /changelog-writer .
gemini-live-api-dev
Use this skill when building real-time, bidirectional streaming applications with the Gemini Live API. Covers WebSocket-based audio/video/text streaming, voice activity detection (VAD), native audio features, function calling, session management, ephemeral tokens for client-side auth, live translation, and all Live…
release-checklist
Pre-release safety audit for the Bifrost repo. Scans database migrations changed in a release for high-scale deadlock / lock-contention risks and for work that blocks application boot time, then produces a pass/warn/fail report with a concrete remediation plan. Invoked with /release-checklist [git-ref-range]. Built to…