LangBot is an open-source platform for connecting language models to instant-messaging services so developers can build chatbots that converse, use tools, and execute tasks. It supports bot management, knowledge bases, plugins, and multiple chat platforms, and the catalogue entries provide skills, MCP tools, and instructions for working with it.
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 langbot-app/LangBot --skill langbot-env-setupgit clone --depth 1 https://github.com/langbot-app/LangBotWrote 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/langbot-app/langbot/langbot-env-setup)<a href="https://agentmods.dev/skills/langbot-app/langbot/langbot-env-setup"><img src="https://agentmods.dev/badge/skills/langbot-app/langbot/langbot-env-setup/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/langbot-app/langbot/langbot-env-setup"><img src="https://agentmods.dev/badge/skills/langbot-app/langbot/langbot-env-setup.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.00067 | $0.00427 |
| Opus 5.5 | $0.00027 | $0.00171 |
| Sonnet 5.5 | $0.00013 | $0.00085 |
| Haiku 4.5 | $0.00007 | $0.00043 |
Grade A, and why
langbot-env-setup 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 2mo 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
LangBot Environment Setup
Use this skill when a task needs LangBot to be in a testable state before product testing or development verification.
Routing
- Shared local variables: read
../.envbefore using URL, path, browser profile, or proxy defaults. - Always start here: read
references/browser-access-selection.mdto choose the browser-control path. - LangBot service checks and startup: read
references/service-startup.md. - Computer Use available: read
references/computer-use.md. This path usually needs less browser/MCP setup. - No Computer Use, browser automation required: read
references/playwright-mcp.md. - GitHub OAuth or persisted login profile: read
references/oauth-browser-profile.md. - WSL-specific notes: read
references/wsl-notes.mdonly when running under WSL. - Proxy setup: read
references/proxy.mdwhen external login, model provider tests, or package downloads time out. - Headless-only automation: use only after a profile already contains a valid LangBot login. Do not ask the agent to enter GitHub credentials or 2FA.
Rules
- Never handle the user's GitHub password, passkey, recovery code, or 2FA secret.
- For OAuth login, open a visible browser and let the user complete the credential steps.
- Reuse a fixed browser profile path so the agent can later access the logged-in LangBot session.
- Keep environment-specific paths and commands in
references/, not in this file. - Treat environment setup as complete only after the target LangBot services are reachable and the browser profile can access the WebUI.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 29 lines · 67 tokens per session scan A 1abaabc72ef5
langbot-env-setup is a skill published in the GitHub repository langbot-app/LangBot (18,715 stars, last pushed yesterday), licensed Apache-2.0. It adds 67 tokens to every session and 427 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for publishartifact, outputiframe, or slackattachhtml.
workspaces
How an Open SWE workspace's sandbox image works and how to change it — create one, edit or fork an existing one, start from scratch, what setupscript and updatescript are for, why a nightly refresh failed, where the build logs are, and how to read a rebuild in progress. Read this whenever someone asks about…
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
connect
Connect this machine's Claude Code to Open SWE, so every session is mirrored into a private Open SWE thread.
thread
Show the Open SWE thread that mirrors this Claude Code session. Use when asked for this session's Open SWE link or thread.