agentmods.dev

langbot-testing

langbot-testing is a skill for Claude Code, Codex from langbot-app/LangBot. It costs 58 tokens per session (923 once invoked), scanned A, original, Apache-2.0.

A testing guide for LangBot's web interface and core product flows. LangBot is an application for building and running AI bots, while a web interface lets you configure and test them in a browser.

In plain words
What is it for?
It helps test chats, model-provider setup, bots, knowledge bases, plugins, skills, MCP tools, agent runners, and performance or reliability scenarios.
Why use it?
It helps verify that product behavior works in a real browser and use backend logs to investigate failures, instead of checking code alone.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 18krepo +121 changed 23d ago A scan SkillSpector: pass 58 tokens original Apache-2.0

Good fit It helps test chats, model-provider setup, bots, knowledge bases, plugins, skills, MCP tools, agent runners, and performance or reliability scenarios.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/langbot-app/langbot/langbot-testing
View source ↗ langbot-app/LangBot space.langbot.app
About the project

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.

langbot-app/LangBot · 18,213 stars · on GitHub · space.langbot.app

Install

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.

Any agent
npx skills add langbot-app/LangBot --skill langbot-testing
Clone the repo
git clone --depth 1 https://github.com/langbot-app/LangBot

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for langbot-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/langbot-app/langbot/langbot-testing/github.svg)](https://agentmods.dev/skills/langbot-app/langbot/langbot-testing)
Your own site
<a href="https://agentmods.dev/skills/langbot-app/langbot/langbot-testing"><img src="https://agentmods.dev/badge/skills/langbot-app/langbot/langbot-testing/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.

agentmods 80×15 button for langbot-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/langbot-app/langbot/langbot-testing"><img src="https://agentmods.dev/badge/skills/langbot-app/langbot/langbot-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 923 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.00923
Opus 5.5 $0.00023 $0.00369
Sonnet 5.5 $0.00012 $0.00185
Haiku 4.5 $0.00006 $0.00092

Measured 23d ago against content hash d5567b5006de, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

langbot-testing 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 23d 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.

skills/skills/langbot-testing/SKILL.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LangBot Testing

Use this skill when an agent needs to verify LangBot behavior through the WebUI instead of only reading code.

Routing

  • General WebUI testing: read references/web-ui-testing.md.
  • Pipeline Debug Chat: read references/pipeline-debug-chat.md.
  • Dify Runner: read references/dify-agent-runner.md.
  • Model provider setup or test button: read references/model-provider-testing.md.
  • Plugin install/runtime/tool/page smoke: read references/plugin-e2e-smoke.md.
  • Local Runner: read references/local-agent-runner.md.
  • Local Runner path coverage: read references/local-agent-runner-coverage.md.
  • Diff-aware Runner QA after code changes: read references/agent-runner-qa-workflow.md.
  • Runner release gate: read references/agent-runner-release-gate.md.
  • Sandbox-backed skill authoring: read references/sandbox-skill-authoring.md.
  • LangRAG knowledge bases: read references/langrag-knowledge-base.md.
  • MCP stdio tool testing: read references/mcp-stdio-testing.md.
  • Performance, reliability, or chaos probes: read references/performance-reliability-testing.md.
  • Cross-repository workspace and release gates: read references/workspace-release-testing.md.
  • Drive a live instance over MCP (not raw HTTP): use the langbot-mcp-ops skill — the instance exposes an MCP server at http://<host>:5300/mcp (reuses API keys). Useful for setting up bots/pipelines/models as test fixtures programmatically.
  • Known failures and fixes: read references/troubleshooting.md.
  • Reusable test groups: run bin/lbs suite list and bin/lbs suite plan <suite-id> before manually assembling a case set.

Rules

  • Read ../.env first and use LANGBOT_FRONTEND_URL and LANGBOT_BACKEND_URL instead of hardcoded ports.
  • If a standalone frontend dev server is running, LANGBOT_FRONTEND_URL may point to LANGBOT_DEV_FRONTEND_URL; otherwise it may point to the backend WebUI.
  • Confirm the backend and frontend are actually running before testing.
  • Run bin/lbs fixture check before fixture-heavy MCP, RAG, multimodal, or plugin smoke tests.
  • For runner externalization release checks, run bin/lbs test run agent-runner-release-preflight before the full agent-runner-release-gate suite so configuration blockers are separated from product failures.
  • Read Manual Readiness in bin/lbs test plan <case-id>; manual_check means the declared preconditions or setup still need operator confirmation for this run.
  • Use an authenticated browser profile prepared by langbot-env-setup.
  • Do not expose API keys, OAuth secrets, tokens, or localStorage token values in output.
  • A WebUI test is not complete until the visible UI result is checked against backend logs or network behavior.
  • A performance result is not complete without metrics evidence and a clear split between LangBot overhead and external provider/tool/network time.
  • A chaos or reliability result is not complete until the fault scope, cleanup, and recovery checks are recorded.
  • For a suite, use bin/lbs suite start <suite-id> to create the suite evidence root, per-case directories, and suite-start.json/suite-start.md handoff files; use bin/lbs test result <case-id> to write final per-case result.json, then run bin/lbs suite report <suite-id> --evidence-dir <dir>.
  • Do not mark a case pass until test result --evidence covers every value in the case's evidence_required.
  • For runner-specific Debug Chat cases, use the case-specific pipeline env declared by automation_pipeline_url_env / automation_pipeline_name_env; do not silently reuse a generic LANGBOT_PIPELINE_URL.

Read the full file on GitHub · 46 lines

Files

What ships with it

60 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.

Changes

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.

  1. 23d ago Changed · +1 lines d5567b5006de
  2. 1mo ago First seen · 45 lines · 58 tokens per session scan A becdd878b0ee

Subscribe to this mod's changes

langbot-testing is a skill published in the GitHub repository langbot-app/LangBot (18,213 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 923 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-08-30.

Browser automationE2E testingLLMTestingagentopenaiqqtelegramwechat
Related

Other skills, from other repositories

web-gui-tester

Use the browser automation tooling available in the session to test web frontends interactively in a purely GUI-based, black-box manner: simulate real user clicks, text input, scrolling, and other actions; use screenshots for visual verification and read-only DOM inspection for cross-validation; and produce a final…

YunTaiHua/illusion-agent · 0 tokens

web-ui-test

Test the IronClaw web UI using the Claude for Chrome browser extension.

suyoumo/ClawProBench · 19 tokens

webqa

Use WebQA to test websites, web pages, URLs, login flows, search flows, forms, navigation, and core user journeys with an AI browser QA agent.

MigoXLab/webqa-agent · 36 tokens

using-win

Use when invoking win-device MCP tools to drive a Windows test machine (agent-fleet project) -- screenshot-and-click UI testing, long-running shell commands, file or process operations, or coordinating exclusive device use across multiple agents.

metahub-tech/agent-fleet · 48 tokens

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

spytensor/openmozi · 35 tokens

browser-testing-with-devtools

Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.

Djtony707/TITAN · 57 tokens