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/abiswas97/gemini-plugin-cc/releasenpx skills add abiswas97/gemini-plugin-cc --skill releasegit clone --depth 1 https://github.com/abiswas97/gemini-plugin-ccWrote 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/skills/abiswas97/gemini-plugin-cc/release)<a href="https://agentmods.dev/skills/abiswas97/gemini-plugin-cc/release"><img src="https://agentmods.dev/badge/skills/abiswas97/gemini-plugin-cc/release.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00361 |
| Opus 5 | $0.00009 | $0.00180 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade B, and why
release scanned grade B with 1 finding 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 5d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
Do not run any commands. What it actually says
Trigger the release pipeline
This skill fires release-draft.yml on CI. The workflow bumps versions, generates the CHANGELOG entry, and opens a release PR. You review and merge that PR; release-publish.yml then tags and creates the GitHub Release.
Validate the argument
The argument must be exactly one of patch, minor, major. If $ARGUMENTS is anything else (empty, misspelled, multiple values), stop and print:
Usage:
/release patch|minor|major
Do not run any commands.
Dispatch the workflow
With a valid bump type, run:
gh workflow run release-draft.yml -f bump=$ARGUMENTS
If the call fails with a permissions error, print:
This skill is maintainer-only. The repository permissions gate release dispatch; your account does not have
actions:writeon abiswas97/gemini-plugin-cc.
Stop.
Show the run
On success, wait a moment, then run:
gh run list --workflow=release-draft.yml --limit=1 --json databaseId,url,status
Print the URL so the user can watch it. Tell them:
- The run will pause on the
releaseenvironment approval gate - They need to approve it in the Actions tab to proceed
- Once approved, it will run CI, generate the CHANGELOG, and open a release PR
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.
- 5d ago First seen · 48 lines · 18 tokens per session scan B 73b98bab0ac2
release is a skill published in the GitHub repository abiswas97/gemini-plugin-cc (47 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 361 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). 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.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers commits since the last tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.
lov-release-via-cicd
Configure CI/CD and publish new versions for Node, Tauri, Vite, shell, and GitHub Release projects. Use when the user asks to setup release workflow, publish a new version, verify macOS signing/notarization, recover a failed GitHub Release, or mentions "release-via-cicd", "配置并发布新版", "签名", "notarize", "GitHub Release"…
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…
ccc-ship
Click-first ship flow. Four actions, one test matrix, one release pipeline, one deploy path. User picks the action, the matrix (or agent) runs, results surface as a checkbox scorecard.