What is journey-deploy?

A deployment-checking stage for the Butterbase app-building workflow. It tests the live app, deployed functions, and sign-in flow after deployment.

Use it to confirm that a deployed app responds, its functions work, and authentication completes successfully, with results saved in the build log.

It catches deployment problems before the project is submitted. It records each check and stops when one fails.

journey-deploy — Skill for Claude Code by butterbase-ai

Install

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.

Any agent

npx skills add butterbase-ai/butterbase-skills --skill journey-deploy

Clone the repo

git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills

Made for: Claude Code.

Or install butterbase-skills, the plugin that ships this one along with the rest of its 40 skills, 33 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/butterbase-ai/butterbase-skills/journey-deploy/github.svg)](https://agentmods.dev/skills/butterbase-ai/butterbase-skills/journey-deploy)

Your own site

<a href="https://agentmods.dev/skills/butterbase-ai/butterbase-skills/journey-deploy"><img src="https://agentmods.dev/badge/skills/butterbase-ai/butterbase-skills/journey-deploy/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/butterbase-ai/butterbase-skills/journey-deploy"><img src="https://agentmods.dev/badge/skills/butterbase-ai/butterbase-skills/journey-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 704 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00075	$0.00704
Opus 5.5	$0.00030	$0.00282
Sonnet 5.5	$0.00015	$0.00141
Haiku 4.5	$0.00007	$0.00070

Measured 1mo ago against content hash 636de121522c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

journey-deploy scanned grade A with 1 finding 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 1mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

1. **Frontend reachable.** If `deployed_url` is set, fetch it via Bash `curl -sS -o /dev/null -w "%{http_code}" <url>`. Expect `200`. Log `<ISO> deploy curl 200 ok` or `... <code> fail`.

skills/journey-deploy/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Journey: Deploy verification

Stage 4 of the guided journey. Verify the deployed app actually works end-to-end.

When to use

Dispatched by journey when current_stage: deploy.
Directly via /butterbase-skills:journey-deploy.

Preflight

If docs/butterbase/03-preflight.md is missing, older than 24 hours, or 00-state.md has app_id: null, invoke butterbase-skills:journey-preflight first. Wait for it to return successfully before proceeding.

Inputs

docs/butterbase/00-state.md — for app_id, deployed_url.
docs/butterbase/02-plan.md — for the function list to smoke.
docs/butterbase/04-build-log.md — to know what shipped.

Procedure

Refresh docs. Call butterbase_docs with topic: "frontend". For end-to-end smoke patterns, also WebFetch https://docs.butterbase.ai/deploy. Skip if cache is fresh.

For each check, log a one-line result to 04-build-log.md. Halt on the first ✗ and ask the user to fix or skip.

Frontend reachable. If deployed_url is set, fetch it via Bash curl -sS -o /dev/null -w "%{http_code}" <url>. Expect 200. Log <ISO> deploy curl 200 ok or ... <code> fail.
Functions respond. For each function in the plan with HTTP trigger, call mcp__butterbase__invoke_function with a representative payload. Expect 2xx. Log per function.
Auth round-trip (if configured). If the plan included OAuth, prompt the user: "Open <deployed_url>, click 'Sign in with <provider>', and confirm you land logged-in. Did it work? (yes/no)". Log the answer.
Function logs clean. Call mcp__butterbase__manage_function action: get_logs for the most recent invocations. Show the user any error-level lines. Ask: "Anything concerning here? (no → continue, yes → fix and re-run)".
If all checks pass, tick - [x] deploy in 00-state.md, set current_stage: submit (if hackathon_mode: true) or current_stage: done (otherwise).
Return to journey orchestrator.

Outputs

Multiple lines in 04-build-log.md.
Updated 00-state.md.

Read the full file on GitHub · 52 lines

Changes

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.

1mo ago First seen · 52 lines · 75 tokens per session scan A 636de121522c

Subscribe to this mod's changes

journey-deploy is a skill published in the GitHub repository butterbase-ai/butterbase-skills (535 stars, last pushed 3d ago), licensed MIT. It adds 75 tokens to every session and 704 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Cloud DevOps and cloud E2E testing Testing agent-skills ai-agents backend-as-a-service claude mcp

mirrord-chaos

Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…

metalbear-co/mirrord · 119 tokens

testing-mwaa-workflow

Tests Amazon MWAA workflow execution end-to-end: trigger a run and monitor it to completion for Provisioned (Python DAG, via Airflow REST API) and Serverless (YAML workflow, via StartWorkflowRun). Verifies the artifact is deployed and parse-ready, triggers with confirmation, polls to terminal state, and on failure…

aws/agent-toolkit-for-aws · 188 tokens

atmos-tests

Author Atmos smoke tests, post-deployment stack checks, and integration tests using type: test, HTTP assertions, shell or script/interpreter checks, require gates, parallel dependencies, matrix cases, and lifecycle hooks. Use for test suites in Atmos configuration, not Go unit tests of Atmos itself.

cloudposse/atmos · 62 tokens

journey-deploy