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-realtimegit 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-realtime)<a href="https://agentmods.dev/skills/butterbase-ai/butterbase-skills/journey-realtime"><img src="https://agentmods.dev/badge/skills/butterbase-ai/butterbase-skills/journey-realtime/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-realtime"><img src="https://agentmods.dev/badge/skills/butterbase-ai/butterbase-skills/journey-realtime.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00062 | $0.00529 |
| Opus 5.5 | $0.00025 | $0.00212 |
| Sonnet 5.5 | $0.00012 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
journey-realtime 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 18d 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
Journey: Realtime
Stage 3h of the guided journey. Enable WebSocket subscriptions per the plan.
When to use
- Dispatched by
journeywhencurrent_stage: realtime. - Directly via
/butterbase-skills:journey-realtime. - Skipped (annotated
(n/a)) if the plan has no Realtime section.
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 Realtime section.docs/butterbase/00-state.md— forapp_id.
Procedure
-
Refresh docs. Call
butterbase_docswithtopic: "realtime". For WebSocket subscription shape and RLS interaction, also WebFetchhttps://docs.butterbase.ai/realtime. Skip if cache is fresh. -
Read the Realtime section. Print it back:
"About to enable realtime on: <tables>. Proceed?". Wait foryes. -
Invoke
butterbase-skills:realtimevia the Skill tool with the realtime plan andapp_id. The wrapped skill callsmanage_realtime action: configureper table and reminds the user that RLS still applies to subscribed rows. -
Verify with
manage_realtime action: get. -
Append one line to
docs/butterbase/04-build-log.md:<ISO timestamp> realtime manage_realtime ok -
Tick
- [x] realtimein00-state.md, setcurrent_stage:to the next unchecked stage. -
Return to
journeyorchestrator (or ask"Continue to the next stage? (yes/no)").
Outputs
- Realtime configured tables.
- One line in
04-build-log.md.
Anti-patterns
- ❌ Enabling realtime on a table whose RLS hasn't been configured — clients will connect but see no events.
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.
- 18d ago First seen · 45 lines · 62 tokens per session scan A 4a7b75bb3689
journey-realtime is a skill published in the GitHub repository butterbase-ai/butterbase-skills (535 stars, last pushed 13d ago), licensed MIT. It adds 62 tokens to every session and 529 once invoked, about $0.0002 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-09-30.
Other skills, from other repositories
butterbase
AI-native, open-source backend-as-a-service with a built-in Model Context Protocol server. Postgres, auth, storage, functions, AI gateway.
run402
Build, deploy and operate full-stack applications with the Run402 CLI. Postgres, auth, storage, functions and hosting with a free prototype tier and an explicit spending allowance. Use for web apps, database-backed sites, APIs and deploy.
run402
Build, deploy and operate full-stack applications with the Run402 CLI. Postgres, auth, storage, functions and hosting with a free prototype tier and an explicit spending allowance. Use for web apps, database-backed sites, APIs and deploy.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
platform-custom-field-generate
Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values per record type; also…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…