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-frontendgit 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-frontend)<a href="https://agentmods.dev/skills/butterbase-ai/butterbase-skills/journey-frontend"><img src="https://agentmods.dev/badge/skills/butterbase-ai/butterbase-skills/journey-frontend/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-frontend"><img src="https://agentmods.dev/badge/skills/butterbase-ai/butterbase-skills/journey-frontend.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.00081 | $0.00950 |
| Opus 5 | $0.00041 | $0.00475 |
| Sonnet 5 | $0.00016 | $0.00190 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
journey-frontend 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 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.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journey: Frontend
Stage 3j of the guided journey. Build (or adopt) and deploy the frontend.
When to use
- Dispatched by
journeywhencurrent_stage: frontend. - Directly via
/butterbase-skills:journey-frontend. - Skipped (annotated
(n/a)) iffrontend_stack: nonein00-state.md.
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/02-plan.md— the Frontend section.docs/butterbase/00-state.md— forapp_id,api_base,frontend_stack.
Procedure
- Refresh docs. Call
butterbase_docswithtopic: "frontend". For framework-specific deploy patterns, also WebFetchhttps://docs.butterbase.ai/frontend. Skip if cache is fresh.
Use @butterbase/sdk
Any frontend that talks to the deployed Butterbase app should use @butterbase/sdk:
- Install:
npm install @butterbase/sdkinside the frontend project. - Initialize:
import { createClient } from '@butterbase/sdk'; const bb = createClient({ apiUrl: import.meta.env.VITE_API_URL, appId: import.meta.env.VITE_APP_ID }); - Auth:
bb.auth.signInWithOAuth({ provider: 'google' }),bb.auth.signOut(),bb.auth.getSession(). - Data:
bb.db.from('posts').select('*').eq('user_id', userId). - Storage:
bb.storage.upload(file), persist the returnedobject_id, resolve download URLs via the SDK at render time. - Realtime:
bb.realtime.from('posts').on('insert', cb).subscribe().
Do NOT hand-roll fetch() against the REST API in a Butterbase frontend — the SDK handles auth headers, presigned URL refresh, realtime reconnection, and type-narrowing. The MCP tools are not for runtime code.
For framework-specific patterns (Next.js Server Components, SvelteKit load functions, etc.), call butterbase_docs with topic: "sdk".
Build and deploy
- Read the Frontend section and
frontend_stackfrom00-state.md. Print:"About to deploy a <stack> frontend for app_id <id>. Proceed?". Wait foryes. - Invoke
butterbase-skills:deploy-frontendvia the Skill tool with the frontend spec,app_id, andapi_base. The wrapped skill scaffolds (if nopackage.jsonexists in./webor chosen path), setsVITE_API_URLandVITE_APP_ID, builds, callscreate_frontend_deployment, thenmanage_frontend action: start_deployment. - Capture the live URL from the response. Show it to the user.
- Append one line to
docs/butterbase/04-build-log.md:<ISO timestamp> frontend manage_frontend <live-url> ok - Also write the live URL into a new
deployed_url:field in00-state.mdfront-matter. - Tick
- [x] frontendin00-state.md, setcurrent_stage: deploy. - Return to
journeyorchestrator (or ask"Continue to deploy verification? (yes/no)").
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 · 65 lines · 81 tokens per session scan A df551d4f43b8
journey-frontend is a skill published in the GitHub repository butterbase-ai/butterbase-skills (533 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 950 once invoked, about $0.0004 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 skills, from other repositories
cli-ux
Use for packages/cli changes that affect command UX, prompts, help, output layout, progress, success, warnings, errors, JSON/stdout/stderr contracts, non-interactive/agent behavior, copy, or tests for those surfaces. Do not load for implementation-only refactors with unchanged CLI surface.
nextjs-on-cloudflare
Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext. Use when starting a Next.js project on Cloudflare, moving an existing app to Workers, choosing between vinext and OpenNext, or setting up vinext for Workers. For setup, migration, or deployment, install vinext's upstream skills with npx skills…
x-lsof
Enhanced lsof (List Open Files) with interactive UI and structured output. View open files, network connections, and processes. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
x-last
Enhanced last command with CSV, JSON, tree view, and interactive UI for viewing login history. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
x-ps
Enhanced ps process viewer with interactive UI, fzf support, AI filtering, and CSV/JSON/TSV output formats. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
netlify-deploy
Deploy web projects to Netlify using the Netlify CLI (npx netlify). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.