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-workflowsgit 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-workflows)<a href="https://agentmods.dev/skills/cap-go/capgo-skills/capgo-release-workflows"><img src="https://agentmods.dev/badge/skills/cap-go/capgo-skills/capgo-release-workflows/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-workflows"><img src="https://agentmods.dev/badge/skills/cap-go/capgo-skills/capgo-release-workflows.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.00155 | $0.01536 |
| Opus 5.5 | $0.00062 | $0.00614 |
| Sonnet 5.5 | $0.00031 | $0.00307 |
| Haiku 4.5 | $0.00015 | $0.00154 |
Grade A, and why
capgo-release-workflows 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 15d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capgo Release Workflows
Set up an end-to-end release system: Capgo OTA for web changes, native builds for binary changes, store publishing, and a CI gate that picks the right path.
When to Use
TRIGGER when:
- The user wants a single release pipeline covering live updates, native builds, and store publishing.
- The user is moving off a hosted release service (Appflow-style) to CI they own.
- The user asks "how does CI know if this needs a store release?"
Do not use when:
- The user needs one operation (upload or promote a bundle, request one build). Use
capgo-release-managementorcapgo-native-builds. - The user is wiring the updater plugin. Use
capgo-live-updates. - The user is migrating off Ionic Appflow specifically. Start with
ionic-appflow-migration, then return here for the pipeline. - The app is not Capacitor.
Building Blocks
| Area | Skill | Key command |
|---|---|---|
| OTA updates | capgo-live-updates, capgo-release-management |
bundle upload, channel promote |
| Native builds on Capgo | capgo-native-builds |
build request |
| Native builds on own runners | capacitor-ci-cd |
Xcode / Gradle / Fastlane |
| Store listing and review | capacitor-app-store, capacitor-apple-review-preflight |
n/a |
Procedure
1. Inventory (inspect, then report)
Find out:
- Which CI system runs (
.github/workflows,.gitlab-ci.yml,bitbucket-pipelines.yml,azure-pipelines.yml). - Whether
@capgo/capacitor-updateris installed with the major that matches@capacitor/core, and whethernotifyAppReady()is called. - The existing Capgo channels (
npx @capgo/cli@latest channel list <appId>) and the default channel. - Where native signing lives (Capgo credentials, CI secrets, Fastlane match).
- Whether store uploads are required, or only internal distribution.
Report the gaps to the user and ask before you choose Capgo Build or their own runners for native builds.
2. Define channels and versioning
- Typical channels:
development(self-assign),staging,production(default). - Use semver bundle versions. In CI, use
--bundle <ver>or--auto-bump patch, plus--version-exists-ok. - Set production to the metadata strategy once, so every upload records its native baseline:
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.
- 15d ago Changed · +40 lines · +87 tokens per session 2a012ac17d51
- 1mo ago First seen · 71 lines · 68 tokens per session scan A 0f49931167da
capgo-release-workflows is a skill published in the GitHub repository Cap-go/capgo-skills (73 stars, last pushed 9d ago), licensed MIT. It adds 155 tokens to every session and 1,536 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-09-03.
Other skills, from other repositories
agent-mobile-release-manager
Specialist subagent: App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta…
mobile-cicd
Fastlane, GitHub Actions for mobile, code signing (iOS provisioning, Android keystores), beta distribution (TestFlight, Firebase App Distribution), and app store submissions. Use when setting up mobile build pipelines, automating releases, or managing signing.
loom-dart
Dart language expertise for idiomatic, production-quality code.
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
nextjs-deployment
Provides comprehensive patterns for deploying Next.js applications to production. Use when configuring Docker containers, setting up GitHub Actions CI/CD pipelines, managing environment variables, implementing preview deployments, or setting up monitoring and logging for Next.js applications. Covers standalone output…
nx-monorepo
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx.