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 skills/felipefontoura/bento/typebotnpx skills add felipefontoura/bento --skill typebotgit clone --depth 1 https://github.com/felipefontoura/bentoWrote 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/felipefontoura/bento/typebot)<a href="https://agentmods.dev/skills/felipefontoura/bento/typebot"><img src="https://agentmods.dev/badge/skills/felipefontoura/bento/typebot.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.00161 | $0.01295 |
| Opus 5 | $0.00081 | $0.00647 |
| Sonnet 5 | $0.00032 | $0.00259 |
| Haiku 4.5 | $0.00016 | $0.00129 |
Grade A, and why
typebot 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: Bearer $TYPEBOT_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You operate the HTTP API of a Typebot stack that is already deployed by bento. Day-2 work: run bot flows, manage typebots, pull results. For the exact endpoint paths and request bodies go to the official docs (linked at the bottom) — they are the source of truth. Your job is to know how to approach it, not to memorize the reference.
When this skill and the docs disagree, the docs win.
Critical — Typebot has two distinct API surfaces on two distinct hosts. The builder (
TYPEBOT_BUILDER_HOST) serves management and results APIs (list, publish, get results) — needs a Bearer token. The viewer (TYPEBOT_VIEWER_HOST) serves chat execution (startChat, continueChat) — public, no auth. Mixing the two hosts is the #1 source of mysterious 404s. Always resolve both before making any call.
When to invoke
- "start / run / continue a typebot conversation"
- "list my typebots / publish a typebot / get results"
- "call the chat API / embed my chatbot"
For getting Typebot running use /bento:deploy.
Discover the instance — don't hardcode
# Builder host (management + results)
ssh "$user@$host" \
"jq -r '.envs.typebot.TYPEBOT_BUILDER_HOST' \$HOME/.config/bento/state.json"
# Viewer host (chat execution)
ssh "$user@$host" \
"jq -r '.envs.typebot.TYPEBOT_VIEWER_HOST' \$HOME/.config/bento/state.json"
Swarm tasks (stack typebot): typebot_typebot_builder.1.* and
typebot_typebot_viewer.1.*. Confirm with docker ps.
Auth — mint a token
Builder endpoints require Authorization: Bearer <token>. Viewer endpoints
are public — no token needed.
Mint: Typebot builder UI → top-right avatar → Settings → API tokens → Create. Copy it once (shown only at creation). Store in an env var, never echo:
export TYPEBOT_TOKEN="<your-token>"
Discover your workspaceId
Most management routes require workspaceId. Fetch it once:
curl -s -H "Authorization: Bearer $TYPEBOT_TOKEN" \
"https://$TYPEBOT_BUILDER_HOST/api/v1/workspaces" | jq '.workspaces[] | {id, name}'
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 · 115 lines · 161 tokens per session scan A 41706e6db719
typebot is a skill published in the GitHub repository felipefontoura/bento (20 stars, last pushed 1mo ago), licensed MIT. It adds 161 tokens to every session and 1,295 once invoked, about $0.0008 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
superplane-changelog
When generating a SuperPlane changelog from merged commits. Use for "what's new" summaries with new integrations, new components/triggers, improvements, security updates, and bug fixes. Output is user-focused markdown in tmp/.
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.
clean-code
Clean-code engineering standards for writing, refactoring, and reviewing code in any programming language. Use this whenever the user asks to write clean code, follow clean-code principles, refactor for clarity, improve naming, reduce complexity or duplication, separate concerns, tighten error handling, work…
pandic-office
Convert Markdown to PDF (or DOCX/EPUB/HTML) using the pandoc CLI. Use when asked to produce a PDF report, brief, summary, or any document where the input is Markdown and the output should be a polished, paginated file.
tmux
Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.