launch-agent

A guided setup for creating a new Quickchat AI Agent from a website or a short interview, then showing its generated settings and testing instructions.

In plain words
What is it for?
Use it to create and configure a new Agent, build its instructions from a website, or prepare it when no website is available.
Why use it?
It removes the need to configure an empty Agent by hand and provides a starting setup from the information you supply.

Skill for Claude CodeCodex

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/quickchatai/quickchat-claude-plugin/launch-agent
Any agent
npx skills add quickchatai/quickchat-claude-plugin --skill launch-agent
Clone the repo
git clone --depth 1 https://github.com/quickchatai/quickchat-claude-plugin

Made for: Claude Code, Codex.

Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 963 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.00109 $0.00963
Opus 5 $0.00055 $0.00481
Sonnet 5 $0.00022 $0.00193
Haiku 4.5 $0.00011 $0.00096

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

Security

Grade A, and why

launch-agent 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 2d 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.

plugins/quickchat/skills/launch-agent/SKILL.md · 91 lines

How it starts

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

Launch a new Agent

Stand up a working Agent in one guided flow. Most people running this have just connected Quickchat and have an empty Agent, so build something before you report anything.

Before you start

  • Ask whether they have a website to build from. That answer picks the path below.
  • Explain this creates a real Agent on the FREE tier (no charge, no card).

Path A — they have a website

  1. Call create_assistant with confirm=true (and name if given). Creation is guarded by confirm=true and capped at 5/hour. Tell the user the new scenario_id.
  2. Call onboard_assistant_from_url with that scenario_id and the URL. Say out loud that this takes 20-60 seconds while it scrapes the site, writes the persona and embeds the content — silence here is where people give up. It OVERWRITES configuration, so run it only on the freshly created Agent, never an established one.
  3. Poll get_assistant_settings until onboarding_from_url_completed is true. If it reports onboarding_progress_tracked false there is no completion signal — read the settings once after ~60s instead.
  4. Show what was generated: the name, the main prompt, the guidelines and the language it picked.

If the URL is rejected as a placeholder or marketplace domain, ask for their own business website rather than retrying the same URL.

Path B — no website

Do NOT create an empty Agent and stop. Interview first, in one short round of questions:

  • What does the business do, and what is it called?
  • Who will be talking to the Agent (customers, members, players, staff)?
  • What tone should it take?
  • What are the top 3 questions it must answer?

Then create a configured Agent in a single call — create_assistant accepts the settings inline:

  • name and one_word_description — what the Agent is called
  • short_description — the main prompt: role, what it helps with, what it must not guess at
  • ai_commands — one short rule per item, from their must-answer questions
  • greeting — the first line a visitor sees
  • language_chosen — the language they answered in

Read the full file on GitHub · 91 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. 2d ago First seen · 91 lines · 109 tokens per session scan A 296b99d05bee

Subscribe to this mod's changes

launch-agent is a skill published in the GitHub repository quickchatai/quickchat-claude-plugin (1 stars, last pushed 8d ago), licensed MIT. It adds 109 tokens to every session and 963 once invoked, about $0.0005 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

customer-support

Use when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or escalation with a handoff packet. NOT the help-center article it links to (that is technical-writing), a win-back program (retention), or the…

ericrisco/rsc-harness · 90 tokens

helpscout-navigator

Use when searching HelpScout tickets, customers, or organizations. Provides correct tool selection, required sequencing, and prevents common mistakes. Triggers on "search helpscout", "find tickets", "check support inbox", "helpscout conversations", "look up customer", "find organization", "customer history".

drewburchfield/help-scout-mcp-server · 65 tokens

deskcrew-support

Run a customer support desk on DeskCrew. Read new tickets, answer from the knowledge base, and file replies for human approval. Use when handling customer support. Agents can also create and run their own bounty board over x402 with no account (the wallet that pays createboard owns it) and pay answering agents 85% on…

webmilmind1/deskcrew-mcp · 72 tokens

deskcrew-bounty-hunter

Earn USDC by answering bounty support tickets on DeskCrew's open board. Read the board free, buy ticket context over x402, draft an answer, submit it, and get paid 85% of the bounty when a human approves. Pays out on Base, Polygon, Avalanche, Sei, or Solana; on Solana the agent needs zero SOL. Since 08-2026 the wallet…

webmilmind1/deskcrew-mcp · 141 tokens

deskcrew-board-owner

Run your own USDC bounty board and pay AI agents to answer your questions. One x402 payment creates the board (no account, the paying wallet owns it), USDC deposits fund tasks, and approving an answer pays the winning agent 85% automatically on Base, Polygon, Avalanche, Sei, or Solana. Use when asked to delegate work…

webmilmind1/deskcrew-mcp · 93 tokens

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

basher83/Zammad-MCP · 61 tokens