Borrowing it
Nothing to install: this file belongs to xobotyi/cc-foundry. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/xobotyi/cc-foundry/master/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/xobotyi/cc-foundryWrote 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/xobotyi/cc-foundry/release)<a href="https://agentmods.dev/skills/xobotyi/cc-foundry/release"><img src="https://agentmods.dev/badge/skills/xobotyi/cc-foundry/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/xobotyi/cc-foundry/release"><img src="https://agentmods.dev/badge/skills/xobotyi/cc-foundry/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01261 |
| Opus 5.5 | $0.00022 | $0.00504 |
| Sonnet 5.5 | $0.00011 | $0.00252 |
| Haiku 4.5 | $0.00006 | $0.00126 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Releases
Every plugin version bump that lands on master ships with a GitHub release. The release notes are the plugin's changelog
— there are no CHANGELOG.md files (see docs/adr/0005). A pushed version bump without a release is an incomplete ship.
When to Release
- After every push to master, check the pushed range for plugin version bumps; create one release per plugin whose version changed.
- The user's authorization to push covers release creation — do not ask a second time.
- Repo-level changes that bump no plugin version (ADRs, root docs,
.dev/tooling, this skill) get no release. - Several plugins bumped in one push → one release each.
Identify What to Release
- Find bumped plugins in the pushed range:
git diff <old-origin-head>..origin/master -- '*/plugin.json'. When the old head is unknown, compare each plugin'splugin.jsonversion against its latest<plugin>-v*tag fromgh release list. - For each bumped plugin, resolve:
- the pushed commit that changed its
plugin.jsonversion — the release target - the previous release tag
<plugin>-v*, if any — the notes range and compare-link anchor
- the pushed commit that changed its
- Collect source material:
git log <prev-tag>..<target> -- plugins/<name>/plus the diff of that range. For a first release, use the commits of the bump itself.
Tag and Title Scheme
- Tag —
<plugin>-v<X.Y.Z>, e.g.the-coder-v1.5.0 - Title —
<plugin> v<X.Y.Z>, e.g.the-coder v1.5.0 - Target — the pushed commit that landed the version bump, as its full 40-character SHA. GitHub rejects an
abbreviated SHA with
HTTP 422 Validation Failedand the misleading triotag_name is not a valid tag,Release.target_commitish is invalid,Published releases must have a valid tag. Resolve it withgit rev-parse <short-sha>; a branch name also works. - Never run
git tag—gh release createcreates the tag on the remote at publish time.
Release Notes
Written for people who install the plugin, not for repo contributors.
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.
- 1mo ago First seen · 104 lines · 55 tokens per session scan A bc4edc5b354d
release is a skill published in the GitHub repository xobotyi/cc-foundry (22 stars, last pushed 7d ago), licensed MIT. It adds 55 tokens to every session and 1,261 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-30.
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
Fully automate a release with version-bump and childhood.
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.
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.