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-cli-usagegit 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-cli-usage)<a href="https://agentmods.dev/skills/cap-go/capgo-skills/capgo-cli-usage"><img src="https://agentmods.dev/badge/skills/cap-go/capgo-skills/capgo-cli-usage/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-cli-usage"><img src="https://agentmods.dev/badge/skills/cap-go/capgo-skills/capgo-cli-usage.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.00200 | $0.02404 |
| Opus 5.5 | $0.00080 | $0.00962 |
| Sonnet 5.5 | $0.00040 | $0.00481 |
| Haiku 4.5 | $0.00020 | $0.00240 |
Grade A, and why
capgo-cli-usage 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 2d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capgo CLI Usage
Route Capgo CLI requests, authenticate the CLI, and connect agents to Capgo.
Facts below were checked against @capgo/cli 8.77 (October 2026). Always run npx @capgo/cli@latest <command> --help before you rely on a rarely used flag.
When to Use
TRIGGER when:
- The user asks "how do I use the Capgo CLI", "which Capgo command does X", or asks about CLI login or auth.
- The user wants Claude, Cursor, ChatGPT, or another agent connected to their Capgo account (MCP).
- The request spans several Capgo areas and the right sub-skill is not clear yet.
- The CLI fails before doing any work (auth, wrong directory, missing
appId).
Do not use when one of these already fits. Switch to it as soon as the scope is clear:
- App updater wiring,
notifyAppReady, orautoUpdate:capgo-live-updates - Bundle uploads, channels, rollouts, rollback, or encryption keys:
capgo-release-management - Native cloud builds and signing:
capgo-native-builds - Organizations, members, 2FA, or security policy:
capgo-organization-management - Multi-product Capgo plans (builds, OTA, and store):
capgo-cloud - Ionic or Capacitor's own MCP tooling, not Capgo:
capacitor-mcp
Secrets and Confirmation
- Never ask the user to paste a Capgo API key, signing password,
.p8key, keystore, or service-account JSON into the chat. Ask them to runnpx @capgo/cli@latest loginthemselves (it opens the browser or asks for the key in a masked prompt), or to setCAPGO_TOKENin their shell or CI secret store. - Do not put secrets in command arguments: they end up in shell history and process lists. Use environment variables, the saved login, or the CLI's interactive prompts.
- If a secret appears in the conversation anyway, do not repeat it, do not write it to a file, and tell the user to revoke it and create a new one.
npx @capgo/cli@latestdownloads and runs the newest CLI from npm. Run it only inside the user's project and with their go-ahead. In CI, pin an exact version.- Ask before any command that changes remote state: uploading a bundle, changing or promoting a channel, deleting apps, bundles, channels, or keys, requesting a build that uploads to a store, and exporting or deleting credentials. Say what will change and for which app and channel.
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.
- 2d ago Changed · +10 lines c2e0dc6748b5
- 4d ago Changed 21c2b3019b6b
- 6d ago Changed · +75 lines · +130 tokens per session ebc36569f71b
- 1mo ago First seen · 47 lines · 70 tokens per session scan A 543d95e2c1bc
capgo-cli-usage is a skill published in the GitHub repository Cap-go/capgo-skills (73 stars, last pushed 2d ago), licensed MIT. It adds 200 tokens to every session and 2,404 once invoked, about $0.0008 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
loom-dart
Dart language expertise for idiomatic, production-quality code.
deploy-edge-ai-model
Deploy machine learning models to edge devices using Google AI Edge Gallery, TensorFlow Lite, ONNX Runtime, and MediaPipe. Covers model quantization (INT8/INT4), on-device inference with Gemma 4 models, Android/iOS deployment via AI Edge Gallery, hardware delegate selection (GPU/NPU/DSP), and performance benchmarking…
capacitor-plugins
Guides the agent through installing, configuring, and using Capacitor plugins from six sources — official Capacitor plugins, Capawesome plugins, Capacitor Community plugins, Capacitor Firebase plugins, Capacitor MLKit plugins, and RevenueCat plugins. Covers installation, platform-specific configuration (Android and…
ionic-appflow-migration
Guides the agent through migrating an existing Ionic Appflow project to Capawesome Cloud. Imports an Ionic Appflow organization export with the Capawesome CLI apps:import command — apps, signing certificates, environments, live update channels, native configurations, store destinations, build automations, and…
capacitor-expert
A comprehensive starting point for AI agents to work with Capacitor. Covers core concepts, CLI, app creation, plugins, framework integration, best practices, storage, security, testing, troubleshooting, upgrading, and Capawesome Cloud (live updates, native builds, app store publishing). Pair with the other Capacitor…
capgo-cloud-migration
Guides the agent through migrating an existing Capacitor project from Capgo to Capawesome Cloud. Detects Capgo usage (the @capgo/capacitor-updater plugin, CapacitorUpdater configuration, and @capgo/cli commands in CI/CD) and provides step-by-step migration: replacing the plugin with @capawesome/capacitor-live-update…