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 butterbase-ai/butterbase-skills --skill journey-deploygit clone --depth 1 https://github.com/butterbase-ai/butterbase-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/butterbase-ai/butterbase-skills/journey-deploy)<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.
<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>- NVIDIA SkillSpector 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.00075 | $0.00704 |
| Opus 5 | $0.00037 | $0.00352 |
| Sonnet 5 | $0.00015 | $0.00141 |
| Haiku 4.5 | $0.00007 | $0.00070 |
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 12d 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`. 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
journeywhencurrent_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— forapp_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_docswithtopic: "frontend". For end-to-end smoke patterns, also WebFetchhttps://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_urlis set, fetch it via Bashcurl -sS -o /dev/null -w "%{http_code}" <url>. Expect200. Log<ISO> deploy curl 200 okor... <code> fail. -
Functions respond. For each function in the plan with HTTP trigger, call
mcp__butterbase__invoke_functionwith 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_logsfor 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] deployin00-state.md, setcurrent_stage: submit(ifhackathon_mode: true) orcurrent_stage: done(otherwise). -
Return to
journeyorchestrator.
Outputs
- Multiple lines in
04-build-log.md. - Updated
00-state.md.
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.
- 12d ago First seen · 52 lines · 75 tokens per session scan A 636de121522c
journey-deploy is a skill published in the GitHub repository butterbase-ai/butterbase-skills (533 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 704 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
chaos-experiment
Design and document chaos engineering experiments. Guide steady state baseline, hypothesis formation, failure injection plans, and results analysis. Use when you say "design a chaos experiment", "plan a game day", "failure injection", "test resilience", or "chaos engineering". Do NOT use for security threat analysis…
load-test-ops
Trigger, monitor, update, profile, and stop Camunda load tests using gh CLI and kubectl directly — no MCP server required.
crabbox-setup
Scaffold an isolated CLOUD dev box per agent (via crabbox + Daytona) for any codebase — the parallel-safe counterpart to dev-local-setup. Each agent gets its own full stack (own DB + dev server) and an in-box browser for e2e, so concurrent loops never collide on ports/state. Sets up the snapshot image, .crabbox.yaml…
deploy-verify
Post-deploy smoke test across browser, Sentry, Supabase, Langfuse, and the public web. Use when "verify deploy", "smoke test production", "post-release check", or "ship or rollback". Deploy + observation loop → workflow-ship-and-observe. npm package release → deploy-npm.
cross-repo-testing
This skill should be used when the user asks to "test a cross-repo feature", "deploy a feature branch to staging", "test SDK against OH Cloud", "e2e test a cloud workspace feature", "test provider tokens", "test secrets inheritance", or when changes span the SDK and OpenHands server repos and need end-to-end…
azure-resource-manager-playwright-dotnet
Management plane SDK for provisioning and managing Microsoft Playwright Testing workspaces via Azure Resource Manager.