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/ssube/conclave/conclave-launchnpx skills add ssube/conclave --skill conclave-launchgit clone --depth 1 https://github.com/ssube/conclaveWhat 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.00046 | $0.00541 |
| Opus 5 | $0.00023 | $0.00270 |
| Sonnet 5 | $0.00009 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
conclave-launch 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.
What it actually says
Launch Conclave on Runpod
Deploy a Conclave workspace pod on Runpod using the GraphQL API.
Prerequisites
RUNPOD_API_KEYenvironment variable set- Conclave Docker image pushed to a registry
Usage
# Basic launch with defaults (A100 80GB, 500GB volume)
bash /opt/conclave/scripts/launch-runpod.sh \
--env NGINX_PASSWORD=your-password \
--env MATRIX_SERVER_NAME=conclave.local \
--env EXTERNAL_HOSTNAME=pod-id-8888.proxy.runpod.net
# Custom GPU and image
bash /opt/conclave/scripts/launch-runpod.sh \
--gpu a6000 \
--image your-registry/conclave:latest \
--volume-size 1000 \
--env NGINX_PASSWORD=your-password \
--env ANTHROPIC_API_KEY=sk-ant-...
# With SSH keys
bash /opt/conclave/scripts/launch-runpod.sh \
--env NGINX_PASSWORD=your-password \
--env SSH_AUTHORIZED_KEYS="ssh-ed25519 AAAA..."
Required Environment Variables
Pass via --env flags:
NGINX_PASSWORD(required) — basic auth password for dashboard/ollama/chromadb-adminMATRIX_SERVER_NAME— Matrix server domain (default: conclave.local)EXTERNAL_HOSTNAME— Pod external hostname for config templates
Optional Environment Variables
ANTHROPIC_API_KEY— for Claude Code and piOPENAI_API_KEY— for pi (OpenAI provider)SSH_AUTHORIZED_KEYS— SSH public keys (newline-separated)DEFAULT_OLLAMA_MODEL— model to pre-pull (default: qwen3-coder:30b-a3b-q8_0)
After Launch
- The script prints the dashboard URL and SSH connection string
- Access the dashboard at
https://{pod-id}-8888.proxy.runpod.net/ - Follow the quick-start guide on the dashboard
- Always ask the user if they want you to launch the SSH tunnel for the Neko browser, this will help them out a lot if they want to use the interactive browser in the Conclave workspace
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.
- 2d ago First seen · 60 lines · 46 tokens per session scan A fcc72e1d5a21
conclave-launch is a skill published in the GitHub repository ssube/conclave (2 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 541 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.
Other skills, from other repositories
agents-sdk
Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks.
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
tool-prompt-optimization
Optimize the description prompts an AI agent reads to learn its built-in tools (the .md files under prompts/tools/). Two halves: (1) measure how much of a prompt is already inferable from the tool's JSON parameter schema + name, to prune redundancy with evidence; (2) house authoring rules for what belongs in a tool…
semantic-compression
Re-encode verbose prose into a dense telegraphic register — punctuation as connectives, label frames, verbless assertions — without losing normativity or precision. Use when compressing system prompts, tool/function descriptions, skill bodies, or agent instructions; reducing token count or context bloat; making…
hosted-agents
This skill should be used when designing hosted or background agent infrastructure: sandboxed execution, remote coding environments, warm pools, session persistence, multiplayer collaboration, self-spawning agents, or Modal-style sandboxes.
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.