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 Cap-go/capgo-skills --skill capgo-release-managementgit clone --depth 1 https://github.com/Cap-go/capgo-skillsWrote 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/cap-go/capgo-skills/capgo-release-management)<a href="https://agentmods.dev/skills/cap-go/capgo-skills/capgo-release-management"><img src="https://agentmods.dev/badge/skills/cap-go/capgo-skills/capgo-release-management/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/cap-go/capgo-skills/capgo-release-management"><img src="https://agentmods.dev/badge/skills/cap-go/capgo-skills/capgo-release-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk 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.00162 | $0.02273 |
| Opus 5.5 | $0.00065 | $0.00909 |
| Sonnet 5.5 | $0.00032 | $0.00455 |
| Haiku 4.5 | $0.00016 | $0.00227 |
Grade A, and why
capgo-release-management 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 11d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capgo Release Management
Ship, promote, roll back, and clean up Capgo OTA bundles from the CLI.
Facts below were checked against @capgo/cli 8.77 (October 2026). Every command accepts -a, --apikey. The appId can be omitted inside a Capacitor project.
When to Use
TRIGGER when:
- The user uploads, lists, deletes, or cleans up bundles, or asks which version a channel serves.
- The user creates or configures channels, promotes staging to production, starts, pauses, or rolls back a progressive rollout, or rolls back a bad release.
- The user asks whether a change is OTA-safe (
bundle compatibility,bundle releaseType). - The user sets up bundle encryption (
key create,key save,--key-v2).
Do not use when:
- The work is app-side updater code or config (
notifyAppReady,autoUpdate,setChannel). Usecapgo-live-updates. - A native binary is needed. Use
capgo-native-builds. - The user manages organizations, members, 2FA, or API-key policy. Use
capgo-organization-management. - The user wants an end-to-end release pipeline design. Use
capgo-release-workflows.
Command Map
| Goal | Command |
|---|---|
| Upload and link | bundle upload [appId] --path ./dist --channel production (comma-separate several channels) |
| Is it OTA-safe? | bundle releaseType [appId] --channel production prints OTA or native |
| Detailed native diff | bundle compatibility [appId] --channel production [--text] |
| What is live | channel currentBundle production [appId] --quiet |
| Promote | channel promote staging production [appId] |
| Roll back | channel set production [appId] --bundle <previous-version> |
| Rollout | bundle upload ... --rollout 10, then channel set ... --rollout-percentage 50 / --rollout-promote / --rollout-rollback |
| Create channel | channel add beta [appId] [--default] [--self-assign] |
| Channel policy | channel set <ch> --disable-auto-update major|minor|patch|metadata|none plus --ios/--android/--dev/--prod/--emulator/--device toggles |
| List | bundle list [appId], channel list [appId] |
| Clean up | bundle cleanup [appId] --bundle 1.0 --keep 3 |
| Delete | bundle delete <version> [appId], channel delete <ch> [appId] |
| Preview QR | app set [appId] --preview once, then get-qr [appId] --channel beta or bundle upload ... --qr-preview |
| Encryption keys | key create, key save --key ./.capgo_key_v2.pub, key delete_old |
| Custom zip / external | bundle zip [appId] --json, bundle encrypt <zip> <checksum>, bundle upload --external <url> |
What ships with it
1 file 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.
- 11d ago Changed e342c97c0c01
- 13d ago Changed · +83 lines · +110 tokens per session 74c42ba2ba1a
- 1mo ago First seen · 54 lines · 52 tokens per session scan A cb8a58fdf9c9
capgo-release-management is a skill published in the GitHub repository Cap-go/capgo-skills (73 stars, last pushed 7d ago), licensed MIT. It adds 162 tokens to every session and 2,273 once invoked, about $0.0006 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
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
apply-semantic-versioning
Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes…
create-github-release
Create a GitHub release with proper tagging, release notes, and optional build artifacts. Covers semantic versioning, changelog generation, and GitHub CLI usage. Use when marking a stable version of software for distribution, publishing a new library or application version, creating release notes for stakeholders, or…
release-notes
Summarize a logical grouping of git commits into plain-language release notes for non-technical readers. Use when the user asks for release notes, what changed, a summary of commits, a plain-English changelog, or an easy-to-read bullet list of work at a specific reading level (default 8th grade). Ask which boundary to…
publish-vscode-extension
Publish a VS Code extension to the VS Code Marketplace and/or Open VSX Registry. Use when the user wants to publish, ship, or release a VS Code extension; audit or improve manifest, listing, or release setup; build or upload a .vsix; set up vsce or ovsx; create a marketplace publisher or Open VSX namespace; configure…
to-release
Prepare a library release on its PR (version, changelog, draft GitHub release) for review, then tag and publish it after you merge.