Borrowing it
Nothing to install: this file belongs to HLND2T/CS2_VibeSignatures. 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/HLND2T/CS2_VibeSignatures/main/.claude/skills/trigger-release-build/SKILL.mdgit clone --depth 1 https://github.com/HLND2T/CS2_VibeSignaturesWrote 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/hlnd2t/cs2_vibesignatures/trigger-release-build)<a href="https://agentmods.dev/skills/hlnd2t/cs2_vibesignatures/trigger-release-build"><img src="https://agentmods.dev/badge/skills/hlnd2t/cs2_vibesignatures/trigger-release-build.svg" alt="Measured on agentmods" 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.00038 | $0.00357 |
| Opus 5 | $0.00019 | $0.00179 |
| Sonnet 5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
trigger-release-build 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 yesterday.
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
Trigger Release Build
Use the bundled script as the only remote-operation entry point. Do not construct an ad-hoc gh workflow run
command, accept a user-supplied SHA, move a tag, edit a Release, cancel work, or bypass source-artifact preflight.
Procedure
-
Extract the requested game version, or use
latestonly when the user explicitly asks for the latest version. -
Select
verify-onlyfor a non-publishing rebuild/verification. Selectpublishonly when the user explicitly asks to publish or retry publication. -
Run from any directory with the mode stated explicitly:
uv run python .claude/skills/trigger-release-build/scripts/trigger_release_build.py <GAMEVER-or-latest> --mode <verify-only-or-publish> -
Report the script's selected version, publication mode, full
SOURCE_SHA, commit subject, and Actions run URL. -
If the script refuses the operation, surface its exact safety reason and stop. Do not bypass repository, auth, version, source-artifact, duplicate-work, or
origin/mainchecks.
Published content is immutable. A retry dispatches the same source identity and relies on the protected publishers'
exact-byte idempotency; it never selects a republish/clobber mode. Any requested generator/config change must already be
merged into origin/main with its complete bin_artifacts/<GAMEVER> tree.
What ships with it
2 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.
- yesterday Changed · +1 lines · -3 tokens per session ab340192bc6e
- 8d ago First seen · 29 lines · 41 tokens per session scan A a14cd009b8f6
trigger-release-build is a skill published in the GitHub repository HLND2T/CS2_VibeSignatures (65 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 357 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-30.
Other skills, from other repositories
build-game-changelog
Design, implement, backfill, audit, and release in-game changelogs with contiguous versioning, deployment provenance, menu-state navigation, accessible toggle, close, and Escape behavior, and responsive release-ledger UI. Use when Codex needs to add or revise a changelog or version screen in a game, reconstruct…
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
release
Automate Godot MCP Native plugin and CLI release. Bumps versions, runs tests, builds packages, creates GitHub Release draft.
flame-harness-build
Phase 8 — bootstrap signing credentials, generate fastlane config from templates, and build + upload signed IPA (TestFlight) and AAB (internal track).
roblox-publish-checklist
Use before publishing or updating a Roblox experience to run evidence-backed release gates for the surfaces that changed.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.