webchat-setup

webchat-setup is a skill for Claude Code, Codex from Cognigy/cognigy-plugin. It costs 41 tokens per session (3,557 once invoked), scanned A, original, MIT.

A setup guide for Cognigy's Webchat v3, an embeddable chat window that lets website visitors talk to an AI agent. The endpoint connects the window to a conversation flow and stores its appearance and behavior settings.

In plain words
What is it for?
Use it to create a Webchat endpoint, connect it to an agent flow, adjust colors and behavior, test the demo page, or obtain embedding details for deployment.
Why use it?
It provides a defined way to create or update the website chat connection without accidentally changing an existing endpoint.

Skill for Claude CodeCodex

Part of the cognigy plugin — 15 skills, 2 agents shipped together

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.

agentmods
npx agentmods add skills/cognigy/cognigy-plugin/webchat-setup
Any agent
npx skills add Cognigy/cognigy-plugin --skill webchat-setup
Clone the repo
git clone --depth 1 https://github.com/Cognigy/cognigy-plugin

Made for: Claude Code, Codex.

Or install cognigy, the plugin that ships this one along with the rest of its 15 skills, 2 agents.

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 webchat-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/cognigy/cognigy-plugin/webchat-setup.svg)](https://agentmods.dev/skills/cognigy/cognigy-plugin/webchat-setup)
Your own site
<a href="https://agentmods.dev/skills/cognigy/cognigy-plugin/webchat-setup"><img src="https://agentmods.dev/badge/skills/cognigy/cognigy-plugin/webchat-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,557 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00041 $0.03557
Opus 5 $0.00020 $0.01778
Sonnet 5 $0.00008 $0.00711
Haiku 4.5 $0.00004 $0.00356

Measured 4d ago against content hash 2b62f2b9d6c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

plugin/skills/webchat-setup/SKILL.md · 328 lines

How it starts

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

Webchat v3 Setup Guide

What is Webchat v3?

Webchat v3 is Cognigy's embeddable chat widget for websites. It connects to a Webchat v3 Endpoint, which links a Flow to the widget and holds all appearance/behavior configuration.

Quick Start — Minimal Webchat

  1. Ensure an agent + flow exist: create_ai_agent { name: "My Agent" }
  2. Create a webchat endpoint: manage_webchat { projectId: "...", flowId: "...", name: "My Webchat" }
  3. The response includes demoWebchatUrl — open it in a browser to test immediately.
  4. Always show demoWebchatUrl to the user by default. Only provide configUrl/embeddingSnippet when asked about embedding or production deployment.

Quick Start — Update Existing Webchat

manage_webchat { endpointId: "...", layout: { colors: { primaryColor: "#0052cc" } }, behavior: { renderMarkdown: true } }

CREATE vs UPDATE:

  • To create: omit endpointId and provide projectId + flowId. A new webchat3 endpoint is always created.
  • To update: provide endpointId. Only the specified fields are changed; everything else is preserved.
  • The tool never auto-detects or modifies existing endpoints. To update, first find the endpointId using list_resources { resourceType: "endpoint", projectId }.

Style Presets

Use stylePreset to apply a predefined look in one call:

manage_webchat { endpointId: "...", stylePreset: "modern" }

classic (default)

  • Chat window: 460px, bot output max-width: 73%, bot output border: on
  • Agent message bg: #ffffff, always scroll, no streaming collation, no progressive rendering, markdown on

modern

  • Chat window: 900px, bot output max-width: 100%, bot output border: off
  • Agent message bg: #ffffff, scroll to last input, streaming collation on, progressive rendering on, markdown on, input collation on

slick

  • Chat window: 600px, bot output max-width: 100%, bot output border: off
  • Agent message bg: #cccccc, scroll to last input, streaming collation on, progressive rendering off, markdown on, input collation on

Read the full file on GitHub · 328 lines

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. 4d ago First seen · 328 lines · 41 tokens per session scan A 2b62f2b9d6c1

Subscribe to this mod's changes

webchat-setup is a skill published in the GitHub repository Cognigy/cognigy-plugin (12 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 3,557 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens