config-vibesurf

config-vibesurf is a skill for Claude Code from vibesurf-ai/claude-surf. It costs 31 tokens per session (536 once invoked), scanned A, original, MIT.

A configuration guide for VibeSurf, covering its API connection and JSON-based workflow management.

In plain words
What is it for?
Use it to check connection status, verify and store an API key, import workflows, export workflows, or run custom workflows.
Why use it?
It removes the need to remember the relevant endpoints and request formats when setting up or moving workflows.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the surf plugin — 21 skills, 1 hook shipped together

Good fit Use it to check connection status, verify and store an API key, import workflows, export workflows, or run custom workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vibesurf-ai/claude-surf/config-vibesurf
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 vibesurf-ai/claude-surf --skill config-vibesurf
Clone the repo
git clone --depth 1 https://github.com/vibesurf-ai/claude-surf

Made for: Claude Code.

Or install surf, the plugin that ships this one along with the rest of its 21 skills, 1 hook.

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 config-vibesurf

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/vibesurf-ai/claude-surf/config-vibesurf"><img src="https://agentmods.dev/badge/skills/vibesurf-ai/claude-surf/config-vibesurf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 536 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.
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.00031 $0.00536
Opus 5 $0.00015 $0.00268
Sonnet 5 $0.00006 $0.00107
Haiku 4.5 $0.00003 $0.00054

Measured 12d ago against content hash 0df2c053fd54, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

config-vibesurf 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 12d 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/config-vibesurf/SKILL.md · 80 lines

What it actually says

Config VibeSurf - VibeSurf Configuration

Overview

Manage VibeSurf API key and workflow configurations. Import, export, and execute custom workflows.

When to Use

  • User needs to set up VibeSurf API key
  • User wants to import a workflow from JSON
  • User needs to export a workflow to JSON

API Endpoints

Base path: $VIBESURF_ENDPOINT/api/vibesurf

API Key Management

Action Method Endpoint Description
Check Status GET /api/vibesurf/status Get VibeSurf connection status
Verify Key POST /api/vibesurf/verify-key Verify and store API key

Workflow Management

Action Method Endpoint Description
Import Workflow POST /api/vibesurf/import-workflow Import workflow from JSON
Export Workflow GET /api/vibesurf/export-workflow/{flow_id} Export workflow to JSON file

Request Examples

Verify API Key

POST /api/vibesurf/verify-key
{
  "api_key": "vs-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}

Import Workflow

POST /api/vibesurf/import-workflow
{
  "workflow_json": "{\"name\": \"My Workflow\", \"description\": \"...\", \"data\": {...}}"
}

API Key Format

VibeSurf API keys must:

  • Start with vs-
  • Be 51 characters total length
  • Example: vs-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Workflow Import/Export

Import

  • Accepts Langflow-compatible JSON format
  • Requires valid VibeSurf API key
  • Returns workflow_id and edit_url

Export

  • Exports workflow to JSON file
  • Removes sensitive data (API keys) automatically
  • Returns file path to exported JSON

Workflow

  1. Check API key statusGET /api/vibesurf/status
  2. Set up API key (if needed) → POST /api/vibesurf/verify-key
  3. Import workflowsPOST /api/vibesurf/import-workflow
  4. Export workflowsGET /api/vibesurf/export-workflow/{flow_id}
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. 12d ago First seen · 80 lines · 31 tokens per session scan A 0df2c053fd54

Subscribe to this mod's changes

config-vibesurf is a skill published in the GitHub repository vibesurf-ai/claude-surf (24 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 536 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-30.