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 agentmods add commands/botpress/skills/adk-shipgit clone --depth 1 https://github.com/botpress/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/commands/botpress/skills/adk-ship)<a href="https://agentmods.dev/commands/botpress/skills/adk-ship"><img src="https://agentmods.dev/badge/commands/botpress/skills/adk-ship.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00017 | $0.00717 |
| Opus 5 | $0.00009 | $0.00358 |
| Sonnet 5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
adk-ship 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 4d 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.
What it actually says
Load the adk skill, then run pre-flight checks before deploying.
This is a deploy-to-production command — treat it as destructive-by-default. Confirm with the user before running adk deploy, even when pre-flight is green. Never pass --yes to adk deploy unless the user has explicitly approved it in this turn.
Workflow
-
Pre-flight (run in parallel where possible):
adk check --format json— must pass with zero errors.adk evals --format json— must pass if any evals exist; if none exist, surface that as a warning and offer/adk-evalbefore shipping.git status— surface uncommitted changes; ask whether to ship the working tree as-is or commit first.adk status --format json— confirm the project is linked to the intended workspace and bot.adk secret --prod --format json— surface unset required prod secrets as warnings unless the user wants CI-strict deploy withadk deploy --require-secrets.adk integrations status --target prod --format jsonandadk plugins status --target prod --format json— block on unavailable/unconfigured enabled dependencies. Checkagent.config.tsfor missing models.- If a project command reports an ADK runtime/package mismatch, run
adk project upgrade --dry-run, show the plan, and get approval beforeadk project upgrade.
-
Summarize. Show a tight pre-flight report: ✅ checks passed, ⚠️ warnings, ❌ blockers. Include the linked bot and a one-line diff summary if there are uncommitted changes.
-
Confirm. Always ask before deploying — the original
/adk-shipinvocation is not consent. If there are blockers, stop and offer to fix each. Otherwise (warnings or fully green), ask: "Ship to ? (yes / no)". -
Deploy. Run
adk deploy. Stream output. Ifadk deployprompts for preflight approval, surface the prompt to the user — do not auto-approve. If deploy warns that required prod secrets are unset, show theadk secret:set <KEY> <value> --prodcommands. If deploy warns that integration versions differ between dev and prod, show the warning and recommendadk integrations copy --from dev --to prod --dry-runbefore any promotion. -
Verify. After deploy, run
adk status --format jsonto confirm the deployed version. Report deployed version and any post-deploy warnings. Note:adk chatruns against the local dev bot, not the deployed one — do not use it as a production smoke test. Direct the user to the Dev Console for live verification. -
Wrap up. Link the user to the Dev Console if a URL is in the deploy output. If the ship fixed a bug, point the user at
/adk-evalto capture a regression eval.
Always re-run pre-flight on every /adk-ship invocation. The filesystem may have changed between invocations (manual edits, git pull, codegen) and there is no reliable way to detect that from inside the conversation.
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.
- 4d ago First seen · 32 lines · 17 tokens per session scan A ea43e2989288
adk-ship is a command published in the GitHub repository botpress/skills (11 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 717 once invoked, about $0.0001 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 commands, from other repositories
deploy
Build, test, deploy with staged rollout.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.
scan
Scan AWS account for cost optimization.
k8s-analysis
You are an expert Kubernetes troubleshooter tasked with investigating pod scheduling issues within a specific namespace. Your goal is to conduct a comprehensive analysis, identify root causes, and provide actionable solutions efficiently and precisely.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.