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 skills add giginet/cc-plugin-catalog --skill releasegit clone --depth 1 https://github.com/giginet/cc-plugin-catalogWrote 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/giginet/cc-plugin-catalog/release)<a href="https://agentmods.dev/skills/giginet/cc-plugin-catalog/release"><img src="https://agentmods.dev/badge/skills/giginet/cc-plugin-catalog/release/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.
<a href="https://agentmods.dev/skills/giginet/cc-plugin-catalog/release"><img src="https://agentmods.dev/badge/skills/giginet/cc-plugin-catalog/release.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00040 | $0.00504 |
| Opus 5.5 | $0.00016 | $0.00202 |
| Sonnet 5.5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
release 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 2mo 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.
What it actually says
Release
Publish a new version of cc-plugin-catalog.
Arguments
- If
$ARGUMENTSspecifies a version number, use that version (e.g./release 2.0.0) - If no version is specified, bump the minor version by 1 (e.g.
1.1.0->1.2.0, patch resets to 0)
Steps
1. Determine the current version
Read the version field from pyproject.toml.
2. Determine the new version
- Use
$ARGUMENTSif provided - Otherwise, increment the minor version by 1 and reset patch to 0
3. Update version strings
Update the version in the following files:
pyproject.toml— theversionfieldsrc/cc_plugin_catalog/__init__.py— the__version__variable
4. Sync lockfile
Run uv sync to ensure uv.lock reflects the updated version.
5. Commit
Commit all changed files (including uv.lock). Commit message: Bump version to X.Y.Z
6. Create a tag
Create a git tag without a v prefix. Example: 1.2.0
7. Push
Push the commit and tag to the remote:
git push origin HEAD
git push origin <tag>
8. Create a GitHub Release
Summarize the changes since the previous tag and create a GitHub Release.
# Get the previous tag
PREV_TAG=$(git tag --sort=-v:refname | head -2 | tail -1)
# Get the commit log since the previous tag
git log ${PREV_TAG}..HEAD --oneline
# Create the GitHub Release using gh CLI
gh release create <new_tag> --title "<new_tag>" --notes "<release notes>"
The release notes should contain a concise bulleted summary of changes since the previous version.
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.
- 2mo ago First seen · 72 lines · 40 tokens per session scan A e2a770ace8af
release is a skill published in the GitHub repository giginet/cc-plugin-catalog (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 504 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.