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.
/plugin marketplace add iamcxa/kc-claude-plugins/plugin install kc-plugin-forgeWrote 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/iamcxa/kc-claude-plugins/kc-plugin-release)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-plugin-release"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-plugin-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.1 | $0.00042 | $0.00484 |
| Opus 5 | $0.00021 | $0.00242 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
kc-plugin-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 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.
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
KC Plugin Release
Keep the release handoff narrow and reproducible. In kc-claude-plugins,
release-please owns version propagation, tags, changelogs, and marketplace
metadata through release-please-config.json, .release-please-manifest.json,
and .github/workflows/release-please.yml. This skill has no release-mutation
authority.
Resolve PLUGIN_ROOT to the directory two levels above this SKILL.md.
Claude Code may expose that directory as ${CLAUDE_PLUGIN_ROOT}; Codex should
use the installed plugin root containing this skill. Do not assume a path under
the user's home directory.
Feature and release PR checks
For a feature PR or the release-please PR, use the packaged exact-head watcher:
bash "$PLUGIN_ROOT/scripts/watch-pr-checks.sh" <pr-number> --repo iamcxa/kc-claude-plugins
The watcher uses the authenticated gh CLI directly, propagates failed checks,
and rejects a result if the PR head changes while checks are running. A missing
host-level monitor is not a reason to bypass the gate.
Post-release local sync
Only after the release PR is merged and the release exists:
- Use the non-Conductor main workspace for
kc-claude-plugins. - Update
mainand leave it clean. The helper refuses another branch, a dirty source, or a local head that differs fromorigin/mainwhen that ref exists. - Run:
bash "$PLUGIN_ROOT/scripts/post-release-sync.sh" <plugin> --repo <main-workspace>
The helper copies the released plugin into both
~/.claude/plugins/local/<plugin> and
~/.codex/local-plugins/<plugin>. It refuses to replace either destination
when that destination is a symlink.
Do not edit release metadata, manufacture a tag, or rewrite marketplace data in this step. If release metadata is wrong, repair the release-please configuration in a separate feature PR and let its release PR publish the fix.
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 · 52 lines · 42 tokens per session scan A 1b44410f9c3b
kc-plugin-release is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 484 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-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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…